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
> 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
Hi there, my name is Remco Nonhebel
I'm writing a program (I called it wpbd) that has to be started by
inetd, okay, I
got that working. This program has to kill another process (called
WPBHost), that's working too, but when the socket is closed, at the end
of wpbd, the WPBHost-program
has to be s
