> This process is the ssh daemon: > root 2988 1 0 Sep04 ? 00:00:00 /usr/sbin/sshd > > Two things: before killing the process with the KILL signal, I would > try killing it with TERM > kill -TERM 2988 > > If that doesn't work then kill the process with the KILL signal. > > I would also use: > /etc/init.d/sshd restart > > This will give the init script a chance to do some cleanup work before > restarting
Do this: kill -TERM 2988 && /etc/init.d/sshd restart and if that doesn't work, do: kill -9 2988 && /etc/init.d/sshd restart ? - Grant > > > I just upgraded ssh and when I try to restart I get: > > > > > > * Stopping sshd ... [ !! ] > > > > > > I don't see anything about it in '/var/log/sshd/current'. How can I > > > figure out what is wrong? I'm a little nervous because I don't want > > > to shut myself out of this remote server. > > > > > > > > > I had a similar issue after a previous update to ssh when I went to > > > restart > > > it to get it to use the new binaries. One of the nice features of sshd is > > > that your current session will say active even if you kill the sshd daemon > > > process. Of course, if you get disconnected then you will not be able to > > > log back in, so it's good to do what you need to quickly if you do need to > > > kill (or if it's really stuck, kill -9) the process. When I had this > > > problem I issued a `kill -9 PID_NUMBER && /etc/init.d/sshd start` - just > > > be > > > sure that you're killing the /usr/sbin/sshd process and not one of your > > > sshd > > > login forks at the same time. > > > > OK, I've got to be really careful here. I see the following processes > > in 'ps -ef': > > > > root 2988 1 0 Sep04 ? 00:00:00 /usr/sbin/sshd > > root 7573 2988 0 07:28 ? 00:00:00 sshd: [EMAIL PROTECTED]/0 > > > > Should I: > > > > kill -9 2988 && /etc/init.d/sshd start > > > > Are you sure? :) > > > > - Grant -- [EMAIL PROTECTED] mailing list
