From owner-freebsd-hackers Wed Nov 8 12:19:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 2506037B4C5 for ; Wed, 8 Nov 2000 12:19:39 -0800 (PST) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id NAA18682; Wed, 8 Nov 2000 13:18:38 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpdAAA5vaqAK; Wed Nov 8 13:18:27 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id NAA25082; Wed, 8 Nov 2000 13:19:07 -0700 (MST) From: Terry Lambert Message-Id: <200011082019.NAA25082@usr08.primenet.com> Subject: Re: SIGALARM is loosing when time are shifted. To: lev@serebryakov.spb.ru Date: Wed, 8 Nov 2000 20:19:07 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG (All) In-Reply-To: <7787.001107@serebryakov.spb.ru> from "Lev Serebryakov" at Nov 07, 2000 06:53:58 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > One my program use alarm() to interrupt some blocking system calls. > I use alarm(1) (one second). Everything works Ok, except cases, when > ntpdate shift time more than 1 second forward. If time is shifted > when alarm are set already, but not generated yet, SIGALARM doesn't > occur at all :( > Is it normal? No. This looks like a bug. When advancing the clock past timed events which are outstanding, it is supposed to trigger those events that would have occurred in the interim. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message