Re: fork/execve

2000-05-03 Thread Matt Fahrner
It's probably not killed by inetd but rather it may be doing a "write()" against the closed socket and getting a SIGPIPE signal. If this is the case you'll need to set up a signal handler to catch or ignore this signal otherwise the process will die. I don't believe inetd does anything if the sock

Re: fork/execve

2000-05-01 Thread Tim Hockin
> To create the new WPBHost process I use fork and execve. When I close > the connection with the client, the WPBHost program is also killed by man setsid -- To unsubscribe: mail -s unsubscribe [EMAIL PROTECTED] < /dev/null