At 10:49 PM 04/12/00 -0700, Doug MacEachern wrote:
On Wed, 12 Apr 2000, Bill Moseley wrote:
Hello,
I noticed on the Apache server-status report a child that is stuck in "G"
(Gracefully finishing) after a SIGUSR1 today. Twelve hours ago.
this could be perl_destruct() hanging while trying
Two followup questions:
1) Would truss show this -- or is there a way to test this?
2) Would you expect the child to survive a kill -9 while hanging?
if the process is in a state where you can't kill -9 or attach with strace
or gdb, etc., i have no idea exactly what triggered that. all
Hello,
I noticed on the Apache server-status report a child that is stuck in "G"
(Gracefully finishing) after a SIGUSR1 today. Twelve hours ago.
I don't have root access on this machine, but I thought I'd run a CGI
script to run as "nobody" and kill off the child. (I've done this once
before
On Wed, 12 Apr 2000, Bill Moseley wrote:
Hello,
I noticed on the Apache server-status report a child that is stuck in "G"
(Gracefully finishing) after a SIGUSR1 today. Twelve hours ago.
I don't have root access on this machine, but I thought I'd run a CGI
script to run as "nobody" and
At 09:25 AM 04/12/00 +0200, Stas Bekman wrote:
On Wed, 12 Apr 2000, Bill Moseley wrote:
I noticed on the Apache server-status report a child that is stuck in "G"
(Gracefully finishing) after a SIGUSR1 today. Twelve hours ago.
Looks like a system problem, what do you see when you attach to a
On Wed, 12 Apr 2000, Bill Moseley wrote:
Hello,
I noticed on the Apache server-status report a child that is stuck in "G"
(Gracefully finishing) after a SIGUSR1 today. Twelve hours ago.
this could be perl_destruct() hanging while trying to cleanup. this
normally isn't a requirement, you
