home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!agate!usenet.ins.cwru.edu!wariat!kf8nh
- From: kf8nh@kf8nh.wariat.org (Brandon S. Allbery)
- Newsgroups: comp.os.linux
- Subject: Re: sigset
- Message-ID: <qaBRXB6w165w@kf8nh.wariat.org>
- Date: Thu, 21 Jan 93 21:26:25 EST
- References: <1993Jan21.075324.21795@runx.oz.au>
- Distribution: world
- Organization: Brandon S. Allbery's Personal System
- Lines: 21
-
- bde@runx.oz.au (Bruce Evans) writes:
- > In article <1993Jan19.235103.23941@cbnewsi.cb.att.com> Kenneth Almquist (ka@h
- > >When reliable signals were added to System V Release 3, the developers
- > >added a new system call named "sigset" rather than changing the
- > (stuff deleted)
- > -Dsigset=signal probably won't work if the application wants reliable
- > signals, either. Linux signal() gives unreliable signals :-(.
-
- I wouldn't call sigset() "reliable signals". (Neither does my SVR3.2 manual!
- It contains a warning that sigset() "reliable" signals aren't really
- reliable and sigaction() is preferred.)
-
- Anyone here remember BSD 4.1c? If I recall correctly, *that* was the origin
- of sigset() --- and it wasn't enough, so BSD4.2 introduced a completely
- different signal mechanism which *was* reliable.
-
- ++Brandon
-
- --
- He's BAAAACK! Brandon S. Allbery kf8nh@kf8nh.wariat.org
- Help stamp out OSF/Motif in our lifetime!
-