From owner-freebsd-bugs Fri Oct 26 8:48:31 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id ED73C37B407; Fri, 26 Oct 2001 08:48:28 -0700 (PDT) Received: (from wollman@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f9QFciA10760; Fri, 26 Oct 2001 08:38:44 -0700 (PDT) (envelope-from wollman) Date: Fri, 26 Oct 2001 08:38:44 -0700 (PDT) From: Message-Id: <200110261538.f9QFciA10760@freefall.freebsd.org> To: prg51@morics.riga.post.lv, wollman@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: i386/31504: nanosleep() strange behavior Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: nanosleep() strange behavior State-Changed-From-To: open->closed State-Changed-By: wollman State-Changed-When: Fri Oct 26 08:21:00 PDT 2001 State-Changed-Why: As PHK explained, the granularity of nanosleep() is tied to the frequency of clock interrupts, and this is not likely to change. POSIX says clearly: # The suspension time may be longer than requested because the argument # value is rounded up to an integer multiple of the sleep resolution or # because of the scheduling of other activity by the system. There is no portable mechanism to determine the precise value of the sleep resolution. The Rationale suggests that it should be less than one second, but I can find no normative text even defining the term. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=31504 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message