🚀 go-pugleaf

In article <1989Nov13.140120.17775@hcr.uucp> of comp.unix.wizards larry@hcr.uucp (Larry Philps) writes:
...
   The other interface appeared in R3 and is accessed via the "sigset" system
   call (same arguments as "signal").  Signal handlers invoked after a sigset
   behave just like Berkeley signals, that is ensuing signals of the same type
   are blocked while the signal handler is running.  Just put a

   #define signal sigset

   at the start of your program and see if that fixes the problems.  Your
   program will certainly be more reliable.


I have been looking at sigset(2) and signal(2) in the SYSV.3 docs. The above
should work. But nowhere in the documentation is the replacing of the
signal call with a sigset call explicitly stated as method of using the new 
signals mechinasm. My problem is that on a OPUS 32532 system running V.3 I
get unresolved references for _sigset when I try the above method. A search
through the libraries doesn't find sigset, signal is in libc; but no sigset.
I already know OPUS didn't implement shared libraries in their V.3, did they
forget the new signals also? If not where did they hide sigset?

----------------------------------------------------------------------------
Steve LeFevre  -  Contel Federal Systems, Information Managment Systems Div.
sfl@wlv.imsd.contel.com    (818) 706-4059          All opinions etc, etc....
----------------------------------------------------------------------------