Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.arch Subject: Re: Spawn is impossible to define (was Re: vfork) Message-ID: <.D+4Y53@ggpc2.ferranti.com> Date: 1 Aug 90 11:41:55 GMT References: <5962@titcce.cc.titech.ac.jp> <5971@titcce.cc.titech.ac.jp> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 11 In article <5971@titcce.cc.titech.ac.jp> mohta@necom830.cc.titech.ac.jp (Masataka Ohta) writes: > >No, of a signal. A state that is also useful in that it solves the race > >conditions inherent in generic UNIX signals without adding the unwanted > >complexity of BSD's reliable signals system. KISS. > And you can't still solve the case I mentioned. Wrong on two counts. Setting a deferred signal (inherited as caught) solves the case *I* mentioned. The one *you* came up with can be solved with normal UNIX signals, and I explained how. If you can't remember a message I posted only a few days ago I'm not going to bother repeating it. -- Peter da Silva. `-_-' +1 713 274 5180. 'U`