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 and sshd, -HUP also doesn't shut down any of the
pflogd/dhclient/cron stuff either. The only process it actually stops is
sndiod, all the others restart on their own.
After running commands #1, #3 and #5; almost everything should be
killed. Command #1 should take care of the vast majority of daemons
started at boot; #3 and #5 are to catch the ones that aren't.
Well, -TERM stops every PID I typed in (the four I didn't being init,
two ksh's and ps itself), so I'm not sure where that leave me. I guess
it's some kind of timing thing or race condition?
Also, FWIW, tapping the power button at this point yields a two second
delay before it does anything (down from the previous ten). Not sure if
that's useful information or not.
