Summary: | sshd startup error message | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | André Terpstra <andre> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED NEEDINFO | ||
Severity: | trivial | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Runscript conf file
Network conf file |
Description
André Terpstra
2006-03-18 22:19:07 UTC
ssh has 'need net' in its init script. If your network isn't/cannot be started at the time when sshd starts, then set RC_NET_STRICT_CHECKING accordingly in /etc/conf.d/rc. If I misunderstood your issue, then include some information about your networking configuration, we can't guess. Created attachment 82525 [details]
Runscript conf file
Created attachment 82526 [details]
Network conf file
That didn't help. In addition I have to slightly correct myself. The order of events is: 1) the net.lo service starts 2) immediately afterwards sshd tries to start with the given error message 3) a few other things happen 4) the net.eth0 service starts net.eth0 is a symlink to net.lo Hopefully I've provided enough additional information now. (In reply to comment #4) > That didn't help. What didn't help? Did you add net.eth0 into default runlevel? I've already written that sshd needs net, if only loopback is running, you need to set RC_NET_STRICT_CHECKING accordingly (RC_NET_STRICT_CHECKING="yes" is not correct for such case). Did you perhaps add sshd into boot runlevel instead of default? That was the problem! sshd was in 2 runlevels: boot and default. I've removed it from boot, restored /etc/conf.d/rc to normal and now it works as it should. It's clear I do not understand the details of runlevels fully. Also, I may have made a mistake after emerging ssh. Anyway, thanks. |