|
|
Posted by petersprc on 11/24/06 04:53
It looks like you won't get the SIGPIPE unless you try to write (or
read) from the closed socket. So, your CGI will probably continue until
it attempts some I/O.
petersprc wrote:
> I think a SIGPIPE starts it, and then mod_cgi will detect that it needs
> to follow with a kill.
>
> Tim Roberts wrote:
> > "petersprc" <petersprc@gmail.com> wrote:
> >
> > >As far as I know, in the event of a disconnect, Apache will send a
> > >SIGTERM to the child, and then, if needed, wait up to approximately 3
> > >seconds and send a SIGKILL. Your CGI could handle the SIGTERM and do
> > >any required cleanup. It could also leave behind a long-running process
> > >using the "at now" command.
> >
> > Is that promised anywhere? In my experience, the only side effect of the
> > disconnect is that the sockets feeding stdin and stdout get disconnected.
> > --
> > Tim Roberts, timr@probo.com
> > Providenza & Boekelheide, Inc.
Navigation:
[Reply to this message]
|