Date: Sun, 18 May 1997 14:52:53 +0800 From: Peter Wemm <peter@spinner.DIALix.COM> To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru> Cc: Bruce Evans <bde@zeta.org.au>, peter@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-lib@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libc/gen sleep.c Message-ID: <199705180652.OAA04790@spinner.DIALix.COM> In-Reply-To: Your message of "Sun, 18 May 1997 10:39:14 %2B0400." <Pine.BSF.3.96.970518102602.566C-100000@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= wrote: > But it is not the only difference. As I say, old sleep restarted again > after signal != SIGALRM (f.e. SIGCHLD), but new sleep terminates! I > suspect this thing break Apache. Apache doesn't fail with non-BSD systems that sleep doesn't restart after non-ALRM signals, eg: sunos, solaris, hpux, digital unix, etc.. Apache doesn't use signals internally other than SIGALRM anyway. (well, the user can send SIGHUP and SIGTERM, but that's an exception, not the normal case during operation) eg: from Digital Unix: If the sleep() function returns because the requested time has elapsed, it returns 0 (zero). If the sleep() function returns because it caught a signal, the function returns the number of seconds remaining in the suspen- sion. I noticed that apache is having a lot of trouble with fin_wait_2 when using keepalive connections to unix netscape3 and doesn't run very well with -X when large files are transferred (more than socket buffer I suspect). I found a mention of this in the docs where it explicitly listed Netscape on FreeBSD as one known rogues that don't do client keepalive properly. Cheers, -Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705180652.OAA04790>