From owner-cvs-lib Sun May 18 00:40:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA16201 for cvs-lib-outgoing; Sun, 18 May 1997 00:40:33 -0700 (PDT) Received: from nagual.pp.ru (ache.relcom.ru [194.58.229.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA16186; Sun, 18 May 1997 00:40:08 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.8.5/8.8.5) id LAA00830; Sun, 18 May 1997 11:38:49 +0400 (MSD) Date: Sun, 18 May 1997 11:38:46 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: Peter Wemm cc: Bruce Evans , 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 In-Reply-To: <199705180652.OAA04790@spinner.DIALix.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-lib@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 18 May 1997, Peter Wemm wrote: > Apache doesn't fail with non-BSD systems that sleep doesn't restart after > non-ALRM signals, eg: sunos, solaris, hpux, digital unix, etc.. This may be caused by another SYSVism, i.e. double features negate each other. > 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) It forks a lot, so got SIGCHLD at least. > 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. Maybe we can keep SYSV behaviour too... Lets fix 'killed by SIGALRM' bug first, then I'll see, how it affects Apache. > 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. It is not a case here, I test it with Lynx alone and Lynx can't use keepalive. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/