RE: [PHP4BETA] Apache bailing out on php4b3
| From: | Samuel Liddicott | Date: | Tue, 23 Nov 1999 09:17:49 +0000 |
| Subject: | RE: [PHP4BETA] Apache bailing out on php4b3 | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-6731@lists.php.net to get a copy of this message | ||
> -----Original Message-----
> From: rwidmer@developersdesk.com [mailto:rwidmer@developersdesk.com]
> Sent: Tuesday, November 23, 1999 05:29 PM
> To: Samuel Liddicott; php
> Subject: RE: [PHP4BETA] Apache bailing out on php4b3
>
>
> Addressed to: "Samuel Liddicott" <sam@campbellsci.co.uk>
> "php" <php4beta@lists.php.net>
>
> ** Reply to note from "Samuel Liddicott" <sam@campbellsci.co.uk>
> Mon, 22 Nov 1999 13:39:03 -0000
> >
> > I find that after a failed kill -SIGHUP to apache (graceful restarted
> > but with bad config/something) that apache wont restart without a
> > killall apache first.
> >
>
> FYI, on a moderm Apache, -SIGHUP kills all the child processes, even if
> they are in the middle of serving a request. -SIGUSR1 will let the
> child processes finish requests they have started, then die before they
> get another one. Much nicer for the clients who are receiving pages
> from you when you reload the server.
I lied too, I don't know why I said SIGHUP I meant SIGUSR1.
> I don't know what version this started with, but I think it was before
> 1.3.6.
I had this with 1.3.6
Sam