From owner-freebsd-current Tue Aug 12 12:48:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA14402 for current-outgoing; Tue, 12 Aug 1997 12:48:32 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA14395 for ; Tue, 12 Aug 1997 12:48:28 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id VAA01292; Tue, 12 Aug 1997 21:48:37 +0200 (MEST) From: Søren Schmidt Message-Id: <199708121948.VAA01292@sos.freebsd.dk> Subject: Re: Error in sleep ! In-Reply-To: from "[______ ______]" at "Aug 12, 97 10:35:07 pm" To: ache@nagual.pp.ru (=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=) Date: Tue, 12 Aug 1997 21:48:37 +0200 (MEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to [______ ______] who wrote: [Charset KOI8-R unsupported, filtering to ASCII...] > On Tue, 12 Aug 1997, S_ren Schmidt wrote: > > > Hmm, we don't even use it correctly ourselves, check /bin/sleep !! > > I have the fear that it also is the case in other places. > > What do you mean exactly? I just look at /bin/sleep and not find > any non-POSIX behaviour... Well to quote sleep(1): The sleep command suspends execution for a minimum of seconds. sleep is used to schedule the execution of other commands (see EXAMPLES below). The sleep utility exits with one of the following values: 0 On successful completion, or if the signal SIGALRM was received. >0 An error occurred. This is not how our sleep(1) functions!, it'll exit on the first signal it gets, because of the change in sleep(3)'s behavior.... > > How on earth did POSIX come up with that behavior ?? > > It was even in early POSIX.1 That doesn't mean they are right :) Now one has to encapsulte sleep(3) in a while loop to get it to actually sleep the specified time, thats plain an simple stupid, and also poses a risk for busy looping, a complete no-no i an *IX system... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end ..