Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!rice!uupsi!sunic!dkuug!dkuugin!shj From: shj@login.dkuug.dk (Stig Jacobsen) Newsgroups: comp.unix.programmer Subject: Re: Detecting exec(2) failing after performing fork(2)? Keywords: pipe, close-on-exec Message-ID: Date: 5 Mar 91 17:43:20 GMT References: <1991Mar1.205944.13198@crc.skl.dnd.ca> <1991Mar4.231540.17644@nat.vu.nl> Sender: news@slyrf.dkuug.dk Lines: 22 maart@nat.vu.nl (Maarten Litmaath) writes: > /* set close-on-exec flag */ >#ifdef NO_FCNTL > ioctl(pp[1], FIOCLEX, (int *) 0); >#else > fcntl(pp[1], F_SETFD, 1); >#endif /* NO_FCNTL */ ... > n = read(pp[0], (char *) &err, sizeof err); > close(pp[0]); > return n == 0 ? 0 : err; Yeah! It was something like this that I wanted, where I get no ugly messages splattering over the parents screen and where I get an error return from the spawn call and not via some signal. A big thanks to you and to everybody else who answered here and in mail. -- Stig Jacobsen shj@login.dkuug.dk / sysadm