| sshd, when started as a standalone daemon, it binds to the port 22, so
| starting another daemon with port 22 is not possible.
correct.
| root 12088 1 0 10:19:15 ? 0:03 /usr/local/sbin/sshd
|
| dies for some reason, the other daemons survive and attach themselves to
| process 1. I am kind of worried about starting and shutting down the
right. all processes need a parent.
| daemon at the startup script such as this:
| kill -KILL `cat $SSHDPID`
why? this kills the "master daemon" (the one listening for incoming
connections), but leaves current connections unaffected (your users will
appreciate this).
| What would be the best way to start and shutdown sshd ensuring all the
| daughter daemons are shut down. Should I go through the ps listing and
you can just send a SIGKILL (I think a SIGINT will work too) to all of the
processes. they'll die, and that's it.
| shut down one at a time before shutting down the "master daemon"? Or is it
| safe to leave it alone for the system sending KILL signals to all the
| processes?
it doesn't matter which order you kill them in.
why would you want to kill all of the daemons running though? at system
shutdown I can see it, but otherwise you'd want at least the current
connection daemons to stay up and running I'd hope.
--
Randomly Generated Tagline:
Most people deserve each other.
