From: utzoo!decvax!cca!v.wales@Ucla-Security@sri-unix Newsgroups: net.unix-wizards Title: sleep(3) interference with sigset(3) Article-I.D.: sri-unix.3007 Posted: Mon Aug 30 20:48:42 1982 Received: Wed Sep 8 03:25:20 1982 From: v.wales at Ucla-Security (Rich Wales) Date: 25 August 1982 1013-PDT (Wednesday) If you're using sleep(3) in conjunction with sigset(3), you might be running into trouble because sleep(3) uses the old "signal" system call instead of the new Berkeley signal-handling stuff. I don't think "signal" and "sigset" were ever designed to coexist peacefully in the same program. To fix this problem, put a version of "sleep" in the "libjobs" library in which the "signal" calls have been replaced by "sigset" calls. Once you do this, any programs that use "-ljobs" will use the new "sleep" (with sigset's instead of signal's), while programs that don't use "-ljobs" will be unaffected. -- Rich