2015/09/22 3:21 "Quartz" :
>>
>> The two daemons you refer to, treat SIGHUP as a "please re-read your
>> configuration files and restart". This is semi-common. This happens to
>> also be the two daemons you are testing this with, causing some
confusino.
>
>> Not
I took that to mean:
1) run (presumably as root) 'time sh /etc/rc shutdown'
2) check 'ps -aux' to see what's still running
3) 'kill -HUP [PID]' for each of the remaining processes
4) check 'ps -aux' again
5) 'kill -TERM [PID]' for each of the remaining processes
6) check 'ps -aux' again
Yes.
On 2015 Sep 21 (Mon) at 09:37:11 -0400 (-0400), Quartz wrote:
:>>I took that to mean:
:>>
:>>1) run (presumably as root) 'time sh /etc/rc shutdown'
:>>2) check 'ps -aux' to see what's still running
:>>3) 'kill -HUP [PID]' for each of the remaining processes
:>>4) check 'ps -aux' again
:>>5) 'kill
The two daemons you refer to, treat SIGHUP as a "please re-read your
configuration files and restart". This is semi-common. This happens to
also be the two daemons you are testing this with, causing some
confusino.
Not everything, but some things will still be running.
It wasn't just syslogd
The two daemons you refer to, treat SIGHUP as a "please re-read your
configuration files and restart". This is semi-common. This happens to
also be the two daemons you are testing this with, causing some confusino.
Not everything, but some things will still be running.
It wasn't just
On Sun, Sep 20, 2015 at 1:45 PM, Matthew Martin wrote:
> On Sep 20, 2015 3:12 PM, "Quartz" wrote:
>>
>> I have a machine where tapping the front panel power button correctly
> halts and powers off the machine however there's a solid 10 second
Oops, I misdescribed init's waiting behavior:
On Sun, Sep 20, 2015 at 5:59 PM, Philip Guenther wrote:
...
> For power off via button, init runs "sh /etc/rc shutdown", then sends
> all processes a SIGHUP, then waits 5 seconds. If there are any
> processes still alive it'll
So, slow /etc/rc.d/* script delaying the /etc/rc shutdown step? Or do
you have some daemon which isn't killed by its rc.d script, nor by
SIGHUP, thus requiring SIGTERM and at least 10 seconds?
This is a test system and it's pretty stock right now. Aside from the
standard services like pf and
On Sun, Sep 20, 2015 at 6:12 PM, Quartz wrote:
>> So, slow /etc/rc.d/* script delaying the /etc/rc shutdown step? Or do
>> you have some daemon which isn't killed by its rc.d script, nor by
>> SIGHUP, thus requiring SIGTERM and at least 10 seconds?
>
> This is a test
For power off via button, init runs "sh /etc/rc shutdown", then sends
all processes a SIGHUP, then waits 5 seconds. If there are any
processes still alive it'll send SIGTERM and wait another 5 seconds.
If any are still alive at that point it'll send'em all SIGKILL and
wait another 5 seconds.
On Sun, Sep 20, 2015 at 7:24 PM, Quartz wrote:
...
>> "time sh /etc/rc shutdown". See what's still running. kill -HUP everything
>>> except init and your session and see what's still running 5 seconds
>>> later.
Hmm, you truncated the suggested steps...
>> OK I'll try
Hmm? How about replicate the process and observe the results?
Well, I wasn't sure if that was the exact/entire process or just a summary.
"time
sh /etc/rc shutdown". See what's still running. kill -HUP everything
except init and your session and see what's still running 5 seconds
later.
OK
Hmm? How about replicate the process and observe the results?
Well, I wasn't sure if that was the exact/entire process or just a summary.
"time
sh /etc/rc shutdown". See what's still running. kill -HUP everything
except init and your session and see what's still running 5 seconds
later.
"time sh /etc/rc shutdown". See what's still running. kill -HUP everything
except init and your session and see what's still running 5 seconds
later.
Hmm, you truncated the suggested steps...
You wrote:
"Hmm? How about replicate the process and observe the results? "time
sh /etc/rc
On Sun, Sep 20, 2015 at 8:10 PM, Quartz wrote:
"time sh /etc/rc shutdown". See what's still running. kill -HUP
everything
>
> except init and your session and see what's still running 5 seconds
> later.
>>
>>
>> Hmm, you truncated the suggested
On Sep 20, 2015 3:12 PM, "Quartz" wrote:
>
> I have a machine where tapping the front panel power button correctly
halts and powers off the machine however there's a solid 10 second
delay after I press the button before anything happens. Is there any way to
speed this
I have a machine where tapping the front panel power button correctly
halts and powers off the machine however there's a solid 10 second
delay after I press the button before anything happens. Is there any way
to speed this process up?
17 matches
Mail list logo