Re: [APC-DEV] APC + Apache SIGHUP
| From: | Hannes Magnusson | Date: | Fri, 09 Oct 2009 13:30:16 +0000 |
| Subject: | Re: [APC-DEV] APC + Apache SIGHUP | ||
| References: | 1 2 3 | Groups: | php.apc.dev |
| Request: | Send a blank email to php-apc-dev+get-227@lists.php.net to get a copy of this message | ||
On Fri, Oct 9, 2009 at 03:27, Nathan Clemons <nathan@livemocha.com> wrote:
> On Thu, Oct 8, 2009 at 3:07 AM, Gopal V <gopalv@php.net> wrote:
>> So basically the apc module init is called again in the parent
>> process after it gets a SIGHUP. It's not that apc is clearing
>> its cache or handling the HUP, apache is essentially doing an
>> internal soft restart.
>>
>> http://httpd.apache.org/docs/2.2/stopping.html#hup
>>
>
> Thanks, I didn't actually realize that it restarted APC/PHP on a
> SIGHUP. Are you familiar with whether or not this occurs during a
> SIGUSR1? The Apache documentation is unclear about module reloading.
> From my testing, it seems like it does, but I'm not completely sure
> about that.
According to Rich Bowen (from the Apache doc team) then SIGUSR1 is a
graceful-restart and Apache will *not* reload the modules.
Note though: Some Linux distros add an 'reload' alias, which sometimes
is graceful and othertimes a restart.. so don't use that :)
According to his quick testing Linux is the only OS which does *not*
reload the modules.. so if you are running BSD/OSX or heaven forbid
something crazy like windows or novell...
-Hannes