From owner-freebsd-hackers Thu Aug 1 16:44:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA06282 for hackers-outgoing; Thu, 1 Aug 1996 16:44:33 -0700 (PDT) Received: from veda.is (root@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA06277 for ; Thu, 1 Aug 1996 16:44:27 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.7.5/8.7.3) id XAA22251; Thu, 1 Aug 1996 23:43:12 GMT From: Adam David Message-Id: <199608012343.XAA22251@veda.is> Subject: Re: missed SIGALRM To: fcurrent@jraynard.demon.co.uk (James Raynard) Date: Thu, 1 Aug 1996 23:43:10 +0000 (GMT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199607211230.MAA00718@jraynard.demon.co.uk> from James Raynard at "Jul 21, 96 12:30:11 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I wrote: > > I have noticed that a SIGALRM can sometimes be missed altogether under certain > > conditions, perhaps as a side-effect of heavy machine load. Thanks to people who responded. :) Since it is clearly not relevant to -current, this is redirected from there. Closer analysis showed that it was not a case of missing alarms, but the return value of time(3) is not guaranteed monotonic so this had to be worked around. Is there any long-range timer which is monotonic across reboots, and is not prone to negative increments under the influence of NTP ? -- Adam David