I'm having trouble forking a long-running process from some code running under mod_perl2.
Everything works for the most part, but it seems that the forked process is holding open handles to Apache's logfiles - this means Apache won't restart while the process is running (I get a 'failed to open logfiles' message).
Here's the code I'm using:
use POSIX; # required for setsid
# Do not wait for child processes to complete
$SIG{CHLD} = 'IGNORE';
# fork (and make sure we did!)
defined (my $kid = fork) or die "Cannot fork: $!\n";
if ($kid) {
return (1, $kid);
}else {
# chdir to /, stops the process from preventing an unmount
chdir '/' or die "Can't chdir to /: $!";
# dump our STDIN and STDOUT handles
open STDIN, '/dev/null' or die "Can't read /dev/null: $!";
open STDOUT, '>/dev/null' or die "Can't write to /dev/null: $!";
# redirect for logging
open STDERR, '>', $log_filename or die "Can't write to log: $!";
# Prevent locking to apache process
setsid or die "Can't start a new session: $!";
# execute the command
exec( $cmd, @args );
die "Failed to exec";
}
Back in the mod_perl1 days, I recall using $r->cleanup_for_exec
to solve this problem, but it doesn't seem to be supported under mod_perl2. (Edit: Apparently it's not required any more..)
Any advice on how to correctly start a long-running process from mod_perl2 without these problems would be greatly appreciated!
$r->cleanup_for_exec
was working fine but in mod_perl2 this is not longer required, so could you please help me to implement this in mod_perl2? Thanks in advance. – Ilianailine