public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Init scripts waiting for deps in progress
Date: Sun, 7 Jan 2007 12:10:41 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0701071150080.20138@iabervon.org> (raw)

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.

Is there some way to teach start-stop-daemon that, if a dependancy fails 
because it is already starting up, this means you should wait for it, not 
give up? The other stuff is a bit odd, but ultimately harmless, aside from 
the fact that stuff gets confused by this situation.

	-Daniel
*This .sig left intentionally blank*
-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2007-01-07 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-07 17:10 Daniel Barkalow [this message]
2007-01-08 10:24 ` [gentoo-user] Init scripts waiting for deps in progress Uwe Thiem
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=Pine.LNX.4.64.0701071150080.20138@iabervon.org \
    --to=barkalow@iabervon.org \
    --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