RE: Re: OS Error.... again and again..
Seker, Chris (CSEKER@row.rownet.nih.gov)
Tue, 23 Sep 1997 15:04:53 -0400
Message-Id: <199709231908.PAA23296@relay.openmarket.com>
From: "Seker, Chris" <CSEKER@row.rownet.nih.gov>
To: brad@clari.net, Mike Baptiste <baptiste@nortel.ca>
Subject: RE: Re: OS Error.... again and again..
Date: Tue, 23 Sep 1997 15:04:53 -0400
how do I unsubscribe?
----------
From: Mike Baptiste[SMTP:baptiste@nortel.ca]
Sent: Tuesday, September 23, 1997 1:01 PM
To: brad@clari.net
Cc: scrantr@ix.netcom.com; stanleyg@cs.bu.edu;
thylmann@m1.sprynet.com; fastcgi-developers@OpenMarket.com
Subject: re:Re: OS Error.... again and again..
You should never send a kill -1 (or 9) to Apache since you often
get zombie
processes.
Its recommended you send kill -TERM (to kill it) or -USR1 to do
a graceful
restart where each child is kept alive until its current request
is
finished.
Mike
In message "Re: OS Error.... again and again..", brad@clari.net
writes:
>Sometimes I have seen the problem appear right out of the gate,
when just
>starting the fastcgi with a kill -1 to apache.
>
>But once it happens it never goes away until the kill -1, is
that consistent
>with the running out of listen queues? SHouldn't some of the
pending
>requests eventually go away, opening up queue slots?
>
>It does happen to *all* requests, so it's not something in one
particular fork
>of the fastcgi, it's in the apache module or the OS.
>