| 1 |
On 07 January 2007 19:10, Daniel Barkalow wrote: |
| 2 |
> I have the following set of init stuff: |
| 3 |
> |
| 4 |
> net.wireless depends on ipw3945d |
| 5 |
> ntp-client depends on net |
| 6 |
> net.wireless automagically starts when the interface "wireless" appears |
| 7 |
> net.wireless is in the boot runlevel |
| 8 |
> |
| 9 |
> When I boot the computer, it starts ipw3945d before net.wireless, but not |
| 10 |
> in time for the "wireless" interface to appear before it tries to start |
| 11 |
> net.wireless. Moments later, the interface appears, and it runs |
| 12 |
> net.wireless again, asynchronously, and it spends a while starting up (it |
| 13 |
> has to find the correct network, and dhcp, etc). |
| 14 |
> |
| 15 |
> While net.wireless is starting up, the system synchronously starts |
| 16 |
> ntp-client, which attempts to start net.wireless; this fails (it's already |
| 17 |
> starting), and so ntp-client fails. Then the asynchronous net.wireless |
| 18 |
> finishes starting, and I have network, but no ntp-client. |
| 19 |
|
| 20 |
You didn't say which runlevel started ntp-client. Assuming it is also in your |
| 21 |
boot runlevel, you can try to move it to your default runlevel. That way, it |
| 22 |
will start a bit later. |
| 23 |
|
| 24 |
Uwe |
| 25 |
|
| 26 |
-- |
| 27 |
A fast and easy generator of fractals for KDE: |
| 28 |
http://www.SysEx.com.na/iwy-1.0.tar.bz2 |
| 29 |
Proof of concept of a TSP solver for KDE: |
| 30 |
http://www.SysEx.com.na/epat-0.1.tar.bz2 |
| 31 |
-- |
| 32 |
gentoo-user@g.o mailing list |
Archives