[gentoo-user] Init scripts waiting for deps in progress

[gentoo-user] Init scripts waiting for deps in progress

[Daniel Barkalow]

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

Re: [gentoo-user] Init scripts waiting for deps in progress

[Uwe Thiem]

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

RE: [gentoo-user] Init scripts waiting for deps in progress

[Nelson, David (ED, PAR&D)]

> -----Original Message-----
> From: Uwe Thiem [mailto:uwix@iway.na]
> Sent: 08 January 2007 10:25
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] Init scripts waiting for deps in progress
> 
> 
> 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 quick and dirty fix may include a sleep statement somewhere for a few
seconds, if needed?

David
Note: These views are my own, advice is provided with no guarantee of
success. I do not represent anyone else in any emails I send to this
list.

-- 
gentoo-user@gentoo.org mailing list