X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Message-ID: <207a01c3c8c6$26445c80$0600000a@broadpark.no>
From: "Gisle Vanem" <giva AT bgnett DOT no>
To: "djgpp" <djgpp AT delorie DOT com>
Subject: pending SIGALRM
Date: Mon, 22 Dec 2003 20:59:46 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Reply-To: djgpp AT delorie DOT com

The documentation says an "alarm(0)" should cancel a
pending SIGALRM, but fail to see how.  
__sigprocmask_pending_signals isn't cleared AFAICS. 
How is this done?

And how should "alarm(x)" behave while a SIGALRM was 
blocked and the first SIGALRM didn't fire? Should the original
signal be raised and new signal again in x seconds?
The doc's (alarm.txh) says "the new alarm delay will supercede 
the prior call.". But cannot see this happening with a little test
program under Win-XP.

--gv