A recent update seems to have broken sshd. It no longer starts when
it should. It seems to refuse to start up unless eth0 is up. For years
I've had the following in /etc/conf.d/rc
RC_NET_STRICT_CHECKING="lo"
According to the comments that means that the "net" service is up as
long as at least one interface (including lo) is up, and sshd used to
obey that setting. But now sshd seems to ignore that and has decided
that it knows better than I do -- it refuses to start when I tell it
to via "/etc/init.d/sshd start", and says "sshd is scheduled to start
when net.eth0 has started". I don't plan on starting net.eth0, but I
want sshd started anyway. If I'd meant "start if you happen to feel
like it" I would have typed
/etc/init.d/sshd start-if-you-happen-to-feel-like-it
How do I get sshd to start?
--
Grant Edwards grant.b.edwards Yow! Will this never-ending
at series of PLEASURABLE
gmail.com EVENTS never cease?
