Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rochester!pt.cs.cmu.edu!ius2.cs.cmu.edu!edw
From: edw@ius2.cs.cmu.edu (Eddie Wyatt)
Newsgroups: comp.unix.questions
Subject: Re: SIGUSR1, SIGUSR2 are pretty useless
Message-ID: <1179@ius2.cs.cmu.edu>
Date: Thu, 28-May-87 09:38:10 EDT
Article-I.D.: ius2.1179
Posted: Thu May 28 09:38:10 1987
Date-Received: Sat, 6-Jun-87 15:40:15 EDT
References: <444@its63b.ed.ac.uk>
Organization: Carnegie-Mellon University, CS/RI
Lines: 16


   You have a lot to learn.   One, do you know about the system calls
signal and sigvec?  As soon as you set up a handler then SIGUSR1 and
SIGUSR2, they have real meaning and usefulness.  I'm not going to go into
all the things you can do.

   Two, there are sychronous and asynchronous messages passing conventions.
What do you think the SIGURG is used for.  There are limitations like the
number of bytes you may send out of band (asychronously) and you must do a
few strange things to enable interrupts to be generated on the socket but
the facility exist, at least in Berkley Unix.

-- 
					Eddie Wyatt

e-mail: edw@ius2.cs.cmu.edu