From owner-cvs-lib Sat May 17 20:06:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA01935 for cvs-lib-outgoing; Sat, 17 May 1997 20:06:28 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA01907; Sat, 17 May 1997 20:06:09 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id NAA20270; Sun, 18 May 1997 13:01:28 +1000 Date: Sun, 18 May 1997 13:01:28 +1000 From: Bruce Evans Message-Id: <199705180301.NAA20270@godzilla.zeta.org.au> To: cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-lib@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libc/gen usleep.c Sender: owner-cvs-lib@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Modified files: > lib/libc/gen usleep.c > Log: > if nanosleep returns too early, loop. usleep() does not have a return > value, it appears as though the semantics of usleep are that it doesn't > return early. (only in the nanosleep code - the setitimer code does this > already) Where do those semantics appear? The old behaviour was to return early. The man page said otherwise, but so does the BSD4.4-Lite man page for sleep(3). usleep.3 is a clone of sleep.3 in in BSD4.4-Lite. Someone fixed the worst bugs in sleep.3 but didn't change usleep.3. The actual behaviour hasn't changed since 386BSD. Bruce