|
|
Posted by David T. Ashley on 11/21/06 15:32
"Tim Roberts" <timr@probo.com> wrote in message
news:ks95m2p4aa4eo09eqv0ngiv9vaju8jvtdd@4ax.com...
> "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.
Ah, and then we're back again to my weak Unix programming skills.
If the stdin socket gets disconnected, I have no idea what will happen (will
it look like an EOF?). I suppose the cgic library takes care of this part
....
But if the stdout gets disconnected, can my CGI-BIN just go blindly using
printf()'s with no ill effects??? ... I'd guess yes.
But in any case, good references would be always be appreciated. I actually
know nothing about sockets and so forth, except that they exist.
Navigation:
[Reply to this message]
|