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 socket is closed unless perhaps you're using the "wait"
option.
- Matt
Remco Nonhebel wrote:
>
> 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 started again. Now there I have a problem. wpbd is
> cummunicating, using the inetd.
>
> 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
> the inetd, and that is exacly NOT what I want. I heard that my newly
> created WPBHost is at that point a member of the inetd. How can I make
> sure that it is not, so that it won't be killed when I close the socket.
>
> If anyone has any ideas, I would be very thankful
> Oh, before I forget, could you please reply to: [EMAIL PROTECTED]
>
> greetings and thanks Remco
>
> --
> To unsubscribe:
> mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
begin:vcard
n:Fahrner;Matt
tel;pager:(603) 639-4142
tel;fax:(603) 443-6190
tel;work:(603) 448-4100 xt 5150
x-mozilla-html:FALSE
url:http://www.gizzy.com/matt
org:Burlington Coat Factory Warehouse;MIS Networking
version:2.1
email;internet:[EMAIL PROTECTED]
title:Manager of Networking
adr;quoted-printable:;;2 South Park St.=0D=0AWillis House;Lebanon;NH;03766;USA
x-mozilla-cpt:;-3648
fn:Matt Fahrner
end:vcard
