Combine that with, for example IPC::Run, and a pumping subprocess, so that you can kill the subprocess if you detect the socket close.

I would, however, caution you, in general, on going down this path, because proxy servers will break this. You may not have a proxy server in place now, but you may want to add one later. Also, the client may be behind a proxy, themselves, and you've got no control over that.

owkay, this might be a possibility then because i control the the users of this app more or less. I haven't used IPC::Run yet so i don't know what you mean by a pumping subprocess, i'll have a look into this tnx.


Jorg

"Do or do not, there is no try" -- Yoda

Michael

ok point taken. So what can I do to prevent that these processes will run forever? There is an odd case that the programs i'm calling go into an endless loop. Can i do a timeout of some sort, and then kill the process off?


Jorg

"Do or do not, there is no try" -- Yoda

It's a little hard to say off-hand as I don't know what your subprocess does. If you have control over the subprocesses source then you could put an alarm in its code and terminate it if it runs for more than X seconds. Or you could do the same thing in the parent (your CGI/modperl handler) where you could do something like (pseudo code):

$SIG{ALRM} = sub { die 'Timeout'; };
alarm( some decent duration );
eval {
   fork the child here
   wait for the child (waitpid() or similar)
   if the child returns reset the alarm (alarm(0))
}; 
if($@) {
    if($@ =~ /Timeout/) {
         # child exceeded authorized run time, so kill it
         kill(15, $child);
    } else {
         handle other fatal problems....
    }
}
[download]

It's up to you to determine what amount of time your child process should normally run, so that you don't interrupt a normally executing process.

Michael