| 1 |
hm. well it *should* cause it to place ifplugd higher in the default |
| 2 |
runlevel, which in turn should cause it to initialize before ntp-client.... |
| 3 |
|
| 4 |
On 8/1/05, Darren Dale <dd55@×××××××.edu> wrote: |
| 5 |
> |
| 6 |
> On Monday 01 August 2005 04:16 pm, The Slash wrote: |
| 7 |
> > you could always try removing ntp-client from default, then remove |
| 8 |
> ifplugd |
| 9 |
> > as well, then put ifplugd back in default, followed by ntp-client, thus |
| 10 |
> > changing the order. It worked for me, anyway. |
| 11 |
> |
| 12 |
> Thanks for the suggestion. I dont understand how this would change |
| 13 |
> anything, |
| 14 |
> it didnt improve things on my system. |
| 15 |
> |
| 16 |
> > |
| 17 |
> > On 8/1/05, Darren Dale <dd55@×××××××.edu> wrote: |
| 18 |
> > > I have an ~x86 system, and use ifplugd to start net.eth0 and/or |
| 19 |
> > > net.wlan0. I |
| 20 |
> > > just updated to baselayout-1.12.0_pre3-r2, and now when I boot, |
| 21 |
> > > ntp-client is |
| 22 |
> > > started before ifplugd. |
| 23 |
> > > |
| 24 |
> > > How can I make ntp-client wait until ifplugd has started? Some people |
| 25 |
> > > have reported problems when RC_PARALLEL_STARTUP="yes", but I have it |
| 26 |
> set |
| 27 |
> > > to no. |
| 28 |
> > > |
| 29 |
> > > Thanks, |
| 30 |
> > > Darren |
| 31 |
> > > -- |
| 32 |
> > > gentoo-laptop@g.o mailing list |
| 33 |
> |
| 34 |
> -- |
| 35 |
> |
| 36 |
> Darren |
| 37 |
> -- |
| 38 |
> gentoo-laptop@g.o mailing list |
| 39 |
> |
| 40 |
> |
| 41 |
|
| 42 |
|
| 43 |
-- |
| 44 |
This is The Slash, signing off **click** |
Archives