From: Uwe Thiem <uwix@iway.na>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Init scripts waiting for deps in progress
Date: Mon, 8 Jan 2007 12:24:43 +0200 [thread overview]
Message-ID: <200701081224.43051.uwix@iway.na> (raw)
In-Reply-To: <Pine.LNX.4.64.0701071150080.20138@iabervon.org>
On 07 January 2007 19:10, Daniel Barkalow wrote:
> I have the following set of init stuff:
>
> net.wireless depends on ipw3945d
> ntp-client depends on net
> net.wireless automagically starts when the interface "wireless" appears
> net.wireless is in the boot runlevel
>
> When I boot the computer, it starts ipw3945d before net.wireless, but not
> in time for the "wireless" interface to appear before it tries to start
> net.wireless. Moments later, the interface appears, and it runs
> net.wireless again, asynchronously, and it spends a while starting up (it
> has to find the correct network, and dhcp, etc).
>
> While net.wireless is starting up, the system synchronously starts
> ntp-client, which attempts to start net.wireless; this fails (it's already
> starting), and so ntp-client fails. Then the asynchronous net.wireless
> finishes starting, and I have network, but no ntp-client.
You didn't say which runlevel started ntp-client. Assuming it is also in your
boot runlevel, you can try to move it to your default runlevel. That way, it
will start a bit later.
Uwe
--
A fast and easy generator of fractals for KDE:
http://www.SysEx.com.na/iwy-1.0.tar.bz2
Proof of concept of a TSP solver for KDE:
http://www.SysEx.com.na/epat-0.1.tar.bz2
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-08 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-07 17:10 [gentoo-user] Init scripts waiting for deps in progress Daniel Barkalow
2007-01-08 10:24 ` Uwe Thiem [this message]
2007-01-08 12:56 ` Nelson, David (ED, PAR&D)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200701081224.43051.uwix@iway.na \
--to=uwix@iway.na \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox