Gentoo Archives: gentoo-laptop

From: Mike Benson <mike@×××××××××.au>
To: gentoo-laptop@l.g.o
Subject: Re: [gentoo-laptop] wireless and service dependencies
Date: Fri, 13 Apr 2007 11:52:32
Message-Id: 200704132149.58076.mike@kambe.com.au
In Reply to: Re: [gentoo-laptop] wireless and service dependencies by Will Briggs
1 On Fri, 13 Apr 2007, Will Briggs wrote:
2 > david wrote:
3 > > Will Briggs wrote:
4 > >> G'day all,
5 > >>
6 > >> I'm having this problem. During startup both sshd and ntpd are not
7 > >> started with a warning: "scheduled to start when net.eth0 is started"
8
9 I get the same behaviour.
10 > >>
11 > >> eth0 is my wired network interface, eth1 is my wireless interface.
12 > >>
13 > >> I rarely used a wired network, often use the wireless network.
14
15 Life for the modern laptop at home :-) Same here.
16 > >>
17 > >> This behaviour is fine, to certain extent, because if net.eth0 comes up
18 > >> I'd be happy to have sshd and ntpd start.
19 > >>
20 > >> However, I also want them to start if and when net.eth1 comes up.
21
22 I have the same question!
23 > >>
24 > >> I have searched for a dependency setting somewhere but can't find. Can
25 > >> anyone point me in the right direction?
26 > >>
27 > >> Cheers,
28 > >>
29 > >> W.
30 > >
31 > > Did you;
32 > > # ln -s net.lo /etc/init.d/net.eth1
33 >
34 > Yes. (Well, on checking it wasn't /etc/init.d/net.eth1 -> net.lo but
35 > /etc/init.d/net.eth1 -> /etc/init.d/net.lo. I've changed that but I
36 > suspect it makes no difference having the path in the symlink)
37
38 It makes no difference (assuming you were in /etc/init.d in the first place).
39 >
40 > > # rc-update add net.eth1 default
41 >
42 > No - but deliberately. I think this may be where I, or the system is
43 > confused. Because unlike a desktop it's not just a matter of bringing
44 > up the /etc/init.d/net.* scripts. I don't want DHCP timeouts etc. when
45 > booting off-line.
46
47 Not only that, but there's some automagic code in the rc scripts that will try
48 to bring the interfaces up without linking it to a soft runlevel. So
49 actually, you're better off not doing it.
50 >
51 > net.eth0 is brought up by netplug
52
53 Actually the message is that net.eth0 is invoking netplug to wait for eth0 in
54 the background. I could never work out why that doesn't work with net.eth1.
55
56 >
57 > net.eth1 is brought up by as I understand it, the ipw3945 module being
58 > loaded which runs the ipw3945 daemon, which runs wpa_supplicant, which
59 > runs the init script (maybe those last two steps are vice versa)
60 >
61 > So, currently:
62 > /etc/init.d/net.eth0 status
63 > * status: inactive
64 >
65 > (which is fine, the wire isn't plugged in)
66 >
67 > /etc/init.d/net.eth1 status
68 > * status: started
69 >
70 > which is fine, but I want sshd and ntpd to have recognised this
71 >
72 > In the end I want the services brought up when either or both of
73 > net.eth0 or net.eth1 are started (by cables being plugged in or wireless
74 > networks coming up etc.)
75 >
76 > Thanks for the response,
77 >
78 > W.
79
80 I guess what we both actually want is for these network dependent services to
81 come up when *any* external network interface is functional. But how?
82
83
84 Regards,
85
86 Mike
87 --
88 gentoo-laptop@g.o mailing list

Replies

Subject Author
Re: [gentoo-laptop] wireless and service dependencies Will Briggs <will@××××××××××××××××××.au>