[gentoo-user] Re: * WARNING: sshd is scheduled to start when net.eth0 has started
As fas as I understand it, this messages means, that the start of net.eth0 is backgrounding, because it can take some ticks. The next init-prozess is starting immediately afterward, before net.eth0 is up. If a init-process is started, before net.eth0 is up (in your case sshd), than it will go in the background, too, and waits, until net.eth0 is up and then it will start. Going in the background and waiting generates the schedule message. Since I put this stuff together on my own, I do not know, if it is correct. Can anyone confirm this? Cheers Marc -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: * WARNING: sshd is scheduled to start when net.eth0 has started
Marc Blumentritt wrote: As fas as I understand it, this messages means, that the start of net.eth0 is backgrounding, because it can take some ticks. The next init-prozess is starting immediately afterward, before net.eth0 is up. If a init-process is started, before net.eth0 is up (in your case sshd), than it will go in the background, too, and waits, until net.eth0 is up and then it will start. Going in the background and waiting generates the schedule message. Since I put this stuff together on my own, I do not know, if it is correct. Can anyone confirm this? Cheers Marc Yes. I had a similar or the same output when there was a faulty netplugd here which was preventing eth0 to start. Then not only ssh but all the services that depend on eth0 were giving this schedule message. I was running my eth manually until I found the problem with after I got help here from this mailing list. Actually I think that OP's problem is eth0, not sshd but I'm just guessing because I haven't enough info. -- Best regards, Daniel -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: * WARNING: sshd is scheduled to start when net.eth0 has started
On Fri, Sep 29, 2006 at 10:59:53AM +0200, Marc Blumentritt wrote: As fas as I understand it, this messages means, that the start of net.eth0 is backgrounding, because it can take some ticks. The next init-prozess is starting immediately afterward, before net.eth0 is up. If a init-process is started, before net.eth0 is up (in your case sshd), than it will go in the background, too, and waits, until net.eth0 is up and then it will start. Going in the background and waiting generates the schedule message. Since I put this stuff together on my own, I do not know, if it is correct. Can anyone confirm this? Cheers Marc -- gentoo-user@gentoo.org mailing list I think you are right, but how to disable the anonying message? -- Shaochun Wang [EMAIL PROTECTED] GPG Fingerprint: 70C2 6945 0E46 E08B 419A 007C AC5C F21F 358A 0833 You can get my publickey from the following url: http://lcs.ios.ac.cn/~scwang/docs/scwangpublickey.gpg -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: * WARNING: sshd is scheduled to start when net.eth0 has started
Shaochun Wang schrieb: On Fri, Sep 29, 2006 at 10:59:53AM +0200, Marc Blumentritt wrote: As fas as I understand it, this messages means, that the start of net.eth0 is backgrounding, because it can take some ticks. The next init-prozess is starting immediately afterward, before net.eth0 is up. If a init-process is started, before net.eth0 is up (in your case sshd), than it will go in the background, too, and waits, until net.eth0 is up and then it will start. Going in the background and waiting generates the schedule message. Since I put this stuff together on my own, I do not know, if it is correct. Can anyone confirm this? Cheers Marc -- gentoo-user@gentoo.org mailing list I think you are right, but how to disable the anonying message? Hmm, i do not think, that this should be disabled. It tells you: Well, I started sshd, but it will only run, when net.eth0 comes up! So if sshd does not start, you know there is a problem with net.eth0 and not sshd. Or so I hope... At first I was irritated, too, but now I just do not care. For me, this message is as good as service foo has been started... Cheers Marc -- gentoo-user@gentoo.org mailing list