2015/09/22 3:21 "Quartz" <qua...@sneakertech.com>: >> >> 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? >
I haven't tried this on openbsd, but I wrote a little tool for someone who was fussing about debian taking too long to shut down: http://joels-programming-fun.blogspot.jp/2014/08/this-is-demonstration-of-way-to.html You'll want to tune some of it, probably, may not need to grep, may want to change the timing. Just remember, writing to a file at shutdown will interfere with the shutdown, especially if you use timing too fast to finish one log entry before the next one starts. And you may want to deliberately kill the process before the shutdown process does the final sync. And don't forget to remove things before you put the thing into production. Joel Rees Computer memory is just fancy paper, CPUs just fancy pens. All is a stream of text flowing from the past into the future.
