From owner-freebsd-current Tue Aug 12 07:39:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA25119 for current-outgoing; Tue, 12 Aug 1997 07:39:37 -0700 (PDT) Received: from lsd.relcom.eu.net (ache@lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA25107 for ; Tue, 12 Aug 1997 07:39:30 -0700 (PDT) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.7/8.8.7) id SAA21021; Tue, 12 Aug 1997 18:39:19 +0400 (MSD) Date: Tue, 12 Aug 1997 18:39:14 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: =?KOI8-R?Q?S=F8ren_Schmidt?= cc: FreeBSD current Subject: Re: Error in sleep ! In-Reply-To: <199708121156.NAA02332@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Aug 1997, Søren Schmidt wrote: > I've noticed sleep is"broken in current.. > Run the little program at the end, and notice that the program exits > the sleep call prematurely if a signal is catched. The remaining > sleep period is not resumed after the signal.. > This works as expected on 2.2.1 and the 10 or so other platforms > I've tested sofar... Hmm. Sleep supposed to exit on _any_ signal per POSIX. Where you find 10 platforms which breaks this rule? -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/