Many of the 'execvp' errors I've seen have been caused by the binary not
being in my path. Check your startup script and make sure the sshd binary
is started by the absolute path (and that the bin actually exists there).
--Matthew
--On Thursday, May 11, 2000 7:38 PM -0700 Ed Lazor <[EMAIL PROTECTED]>
wrote:
>
> ssh has stopped letting me in. When I tried to do a restart, it shutdown
> ok, but fails on startup with the error message:
>
> Starting ssh services: execvp: No such file or directory
>
> Any ideas? I haven't made any system changes at all, so I'm concerned I
> may have a hacker doin stuff to the system.
>
> -Ed
__________________________________________________________________
Matthew W. Mauzy
Systems Administrator
Applied Math @ UNC-CH
email : [EMAIL PROTECTED] pager : [EMAIL PROTECTED]
(W) 919.962.9819 www.amath.unc.edu/~mauzy/ (P) 919.216.6289
__________________________________________________________________
