Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <46D56542.50109@o-rourke.org>
Date: Wed, 29 Aug 2007 13:23:30 +0100
From: John ORourke <john-modperl@o-rourke.org>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Matthieu FEREYRE <matthieu.fereyre@sagem.com>
CC: Stephane GUIBOUD-RIBAUD <stephane.guiboud-ribaud@st.com>,
 modperl@perl.apache.org
Subject: Re: Restarting Apache2.2 from PERL
References: 
 <OF53DB35A9.0044D236-ONC1257346.0041DFE1-C1257346.00423445@sagem.com>
In-Reply-To: 
 <OF53DB35A9.0044D236-ONC1257346.0041DFE1-C1257346.00423445@sagem.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Envelope-From: john-modperl@o-rourke.org

Matthieu FEREYRE wrote:
>
> kill -USR1 apache_pid
>
> do that extremly well but apache doesn't have the rights to launch it 
> from perl !
>

Try writing a script which does it - eg.

#!/bin/sh
/etc/init.d/apache restart

put that somewhere and make it setuid root, then in your perl code call

system("/path/to/your/script &");

which would launch it in the background and return control sensibly, I 
think.

The 2 flaws are [1] you have no way to feed back success to the user - 
you could put a Refresh header in the returned page to jump to a status 
page - and [2] any script or user on your server would be able to 
restart it by running the setuid root script.

cheers
John