Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!caen!spool.mu.edu!uunet!mcsun!unido!nixpbe!nixsin!koerber.sin@sni.de
From: koerber.sin@sni.de (Mathias Koerber)
Newsgroups: comp.unix.wizards
Subject: sigset against signal
Message-ID: <1957@nixsin.UUCP>
Date: 5 Jun 91 07:51:26 GMT
Sender: koerberm@nixsin.UUCP
Reply-To: koerber.sin@sni.de
Organization: Siemens Nixdorf Information Systems (Singapore) Pte Ltd
Lines: 9

Since sigset is available, I'm using this instead of signal. Now the sigset
manpage tells me not to intermix sigset(2)/sighold(2)/sigrelse(2)... with the
traditional signal(2) call for one given signal.

Often I'm using alarm()/SIGALRM to provide my own timeout, and at the same
time use sleep(3C) in my programs. Isn't sleep using signal(2) instead of
sigset(2), and why isn't there a problem there. (Or is there only I
don't know it?). The man-page is a bit vague about compatibility of
traditional functions using signal(2) and the newer sigset.