From owner-freebsd-current Tue Aug 12 13:14:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA16591 for current-outgoing; Tue, 12 Aug 1997 13:14:04 -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 NAA16582 for ; Tue, 12 Aug 1997 13:14:00 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id WAA01401; Tue, 12 Aug 1997 22:13:16 +0200 (MEST) From: Søren Schmidt Message-Id: <199708122013.WAA01401@sos.freebsd.dk> Subject: Re: Error in sleep ! In-Reply-To: <199708121633.JAA25574@phaeton.artisoft.com> from Terry Lambert at "Aug 12, 97 09:33:36 am" To: terry@lambert.org (Terry Lambert) Date: Tue, 12 Aug 1997 22:13:16 +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 Terry Lambert who wrote: > > I've noticed sleep is"broken in current.. > > Run the little program at the end, and notice that the program exits=20 > > 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... > > Type "man siginterrupt". Hmm, then that man page is in error too in -current :( -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end ..