From owner-cvs-lib Sun May 18 02:48:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA22493 for cvs-lib-outgoing; Sun, 18 May 1997 02:48:01 -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 CAA22404; Sun, 18 May 1997 02:44:36 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.8.5/8.8.5) id NAA01312; Sun, 18 May 1997 13:29:09 +0400 (MSD) Date: Sun, 18 May 1997 13:29:06 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: Bruce Evans cc: peter@spinner.dialix.com, cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-lib@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libc/gen sleep.c In-Reply-To: <199705180901.TAA31228@godzilla.zeta.org.au> 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, Bruce Evans wrote: > >Hmm. Perhaps install a temporary dummy SIGALRM handler in the sleep.c stub > >so that it doesn't die if there isn't one. The old setitimer way doesn't > >mess with alarm(2), using nanosleep() wont change that. > > Why would a program generate alarms without installing an alarm handler? They assume sleep() install one for them. It is commonly used way to terminate sleep() in a child since not all sleep implementations terminates by other signals. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/