Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!umich!yale!cs.utexas.edu!usc!snorkelwacker!mit-eddie!uw-beaver!ubc-cs!alberta!myrias!dab From: dab@myrias.com (Danny Boulet) Newsgroups: comp.arch Subject: Re: Spawn is impossible to define (was Re: vfork) Message-ID: Date: 7 Aug 90 05:39:13 GMT References: <5962@titcce.cc.titech.ac.jp> <5971@titcce.cc.titech.ac.jp> <.D+4Y53@ggpc2.ferranti.com> <5978@titcce.cc.titech.ac.jp> Organization: Myrias Research Corporation Lines: 16 In article peter@ficc.ferranti.com (Peter da Silva) writes: >What, to have the signal SIG_DFL in the child and SIG_IGN in the parent? >You call "signal(dummy, SIGwhatever)" where dummy() just resets the signal >and ignores it, then call spawn. I explained that three messages back, >now. I'm not responsible for your memory... perhaps you should save these >articles. The problem with this approach is that the parent may not want to ever run with the signal set to SIG_DFL. For example, if the parent wants to run with ^C always disabled but wants to start a child with ^C enabled, the scheme you propose creates a window for the ^C to sneak through (not a very big window but I'm constantly amazed at how good interrupts are at finding windows). >Peter da Silva. `-_-' >+1 713 274 5180. 'U` >