-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 07 January 2004 23:10, Gary Denslow wrote:
this is working for me. thanks for the suggestion!
use POSIX;
my $sigset = POSIX::SigSet-new();
my $action = POSIX::SigAction-new(
'sigUSR2_handler',
$sigset,
this is working for me. thanks for the suggestion!
use POSIX;
my $sigset = POSIX::SigSet-new();
my $action = ""> 'sigUSR2_handler', $sigset, POSIX::SA_NODEFER,);
POSIX::sigaction(POSIX::SIGUSR2, $action);
sub sigUSR2_handler { warn "got SIGUSR2\n";}
On Tuesday 30 December 2003 22:35, Gary Denslow wrote:
anyway, the signal handler is working on solaris. my problem is that on my
linux setup the signal handler is being completely ignored. i send a USR2
to the root httpd process and the signal handler is not executed at all...
I think your
a signal handler for USR2 has been setup in startup.pl, but
sending
a USR2 to the root httpd process does not result in the execution of
the
signal handler; apache: 1.3.29; mod_perl: 1.29; perl: 5.8.2;
#
output of uname -a
Linux
Hi there,
On Tue, 30 Dec 2003, Gary Denslow wrote:
a signal handler for USR2 has been setup in startup.pl, but sending
a USR2 to the root httpd process does not result in the execution of
the signal handler
apache: 1.3.29; mod_perl: 1.29; perl: 5.8.2
I think signal handling is a bit of a
hey ged
yestserday i saw the post that you referenced. if i understand that post, the user was noticing that when the initial httpd process is started, it forks to create another httpd root process. the PID for this 2nd root httpd process is written to the webserver's PID file and this 2nd root
