I pluged signal(SIGTERM, SIG_IGN) into cronolog and that solved the
problem for me.
arkadi.
So is there any progress with the issue or just nobody is interested?
arkadi.
On my medium busy FreeBSD and Linux servers I noticed that sometimes
apache leaves previous instance children in non-working state after
restart. Examination with ps/strace/truss shows that all of them
are writing to
On Tue, Mar 08, 2005 at 01:22:46PM -0500, Jeff Trawick wrote:
On Tue, 08 Mar 2005 19:00:05 +0200, Arkadi Shishlov [EMAIL PROTECTED] wrote:
So is there any progress with the issue or just nobody is interested?
me interested? yes
me have time right now? no
The more investigation work you
On Tue, Mar 08, 2005 at 08:11:10PM +, Joe Orton wrote:
The bug being discussed here is the same as this PR, right?
http://issues.apache.org/bugzilla/show_bug.cgi?id=26467
Yes.
arkadi.
Ah, and yes, Apache 1.3 on FreeBSD 4.9 is compiled with -DBUFFERED_LOGS.
Apache 2.0 on Linux, which is less prone to getting stuck, is from
unstable Debian package, compiled without buffered logs.
arkadi.
Hi.
I believe there is a bug in Apache which makes some child processes
stuck at graceful restart.
On my medium busy FreeBSD and Linux servers I noticed that sometimes
apache leaves previous instance children in non-working state after
restart. Examination with ps/strace/truss shows that all of
On Sun, Feb 27, 2005 at 10:51:12AM -0500, Jeff Trawick wrote:
On Sun, 27 Feb 2005 12:52:53 +0200, Arkadi Shishlov [EMAIL PROTECTED] wrote:
On my medium busy FreeBSD and Linux servers I noticed that sometimes
apache leaves previous instance children in non-working state after
restart
