> > My host is pretty good about issuing commands for me. Any ideas
> > there?
> >
> > - Grant
> start sshd manually to get back in. something like '/usr/bin/sshd -p 3'
> (that would listen on port 3 for ssh connections)
> ("absolute path is necessary for re-exec")
>
> I still don't know what happened; here's what I can do:
> ===================================================================
> [EMAIL PROTECTED] ~ $ ssh [EMAIL PROTECTED]
> Last login: Mon Sep 10 14:23:18 2007 from pascal.spore.ath.cx
> davey ~ # ps -eaf | grep sshd
> root 28869 1 0 14:23 ? 00:00:00 /usr/sbin/sshd
> root 29147 28869 0 14:34 ? 00:00:00 sshd: [EMAIL PROTECTED]/0
> root 29173 29152 0 14:34 pts/0 00:00:00 grep --colour=auto sshd
> davey ~ # kill -9 28869
> davey ~ # ps -eaf | grep sshd
> root 29147 1 0 14:34 ? 00:00:00 sshd: [EMAIL PROTECTED]/0
> root 29186 29152 0 14:35 pts/0 00:00:00 grep --colour=auto sshd
> davey ~ # /etc/init.d/sshd restart
> * Stopping
> sshd ... [ !! ]
> davey ~ # /etc/init.d/sshd zap
> * Manually resetting sshd to stopped state.
> davey ~ # /etc/init.d/sshd start
> * Starting
> sshd ... [ ok ]
> davey ~ # exit logout
> Connection to davey closed.
> [EMAIL PROTECTED] ~ $ ssh [EMAIL PROTECTED]
> Last login: Mon Sep 10 14:34:26 2007 from pascal.spore.ath.cx
> davey ~ # exit
> logout
> Connection to davey closed.
> [EMAIL PROTECTED] ~ $
> =====================================================================
> as you can see, it worked fine for me. I even make sure to use -9.
>
> good luck, grant
Thank you but doesn't it look like there must be a problem that is
preventing my sshd from starting? Won't '/usr/bin/sshd -p 3' just
fail, or is that more likely to work than '/etc/init.d/sshd start'?
Also, is '/usr/bin/sshd' sufficient? Why not port 22?
- Grant
--
[EMAIL PROTECTED] mailing list
