5 messages in ru.sysoev.nginxRe: Safe to kill old pid's?
FromSent OnAttachments
Sam GhodsOct 26, 2006 5:03 am 
Igor SysoevOct 26, 2006 6:01 am 
Sam GhodsOct 26, 2006 6:04 am 
Igor SysoevOct 26, 2006 7:39 am 
Aleksandar LazicOct 26, 2006 10:09 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Safe to kill old pid's?Actions...
From:Sam Ghods (cept@public.gmane.org)
Date:Oct 26, 2006 6:04:50 am
List:ru.sysoev.nginx

Running Centos 4.4 x86_64. Other commands I can run instead?

-Sam

On Oct 26, 2006, at 6:01 AM, Igor Sysoev wrote:

On Thu, 26 Oct 2006, Sam Ghods wrote:

If I did a kill -HUP on the nginx master process, and a few days later there are still a couple processes that still say "nginx: worker process is shutting down", is it safe to simply run a kill command on this individual worker processes? Will it interrupt nginx or make it unstable in any way?

You can kill -TERM or kill -INT them. It's safe.

Any idea why this might occur?

If you running using FreeBSD, what do the commands

ps ax -o pid,ppid,%cpu,vsz,wchan,command|egrep '(nginx|PID)'

fstat | grep 'nginx.*tcp' | awk '{print $3}' | sort | uniq -c

show ?