Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-laptop
Navigation:
Lists: gentoo-laptop: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-laptop@g.o
From: Mike Benson <mike@...>
Subject: Re: wireless and service dependencies
Date: Fri, 13 Apr 2007 21:49:57 +1000
On Fri, 13 Apr 2007, Will Briggs wrote:
> david wrote:
> > Will Briggs wrote:
> >> G'day all,
> >>
> >> I'm having this problem.  During startup both sshd and ntpd are not
> >> started with a warning: "scheduled to start when net.eth0 is started"

I get the same behaviour.
> >>
> >> eth0 is my wired network interface, eth1 is my wireless interface.
> >>
> >> I rarely used a wired network, often use the wireless network.

Life for the modern laptop at home :-) Same here.
> >>
> >> This behaviour is fine, to certain extent, because if net.eth0 comes up
> >> I'd be happy to have sshd and ntpd start.
> >>
> >> However, I also want them to start if and when net.eth1 comes up.

I have the same question!
> >>
> >> I have searched for a dependency setting somewhere but can't find. Can
> >> anyone point me in the right direction?
> >>
> >> Cheers,
> >>
> >> W.
> >
> > Did you;
> > # ln -s net.lo /etc/init.d/net.eth1
>
> Yes. (Well, on checking it wasn't /etc/init.d/net.eth1 -> net.lo but
> /etc/init.d/net.eth1 -> /etc/init.d/net.lo.  I've changed that but I
> suspect it makes no difference having the path in the symlink)

It makes no difference (assuming you were in /etc/init.d in the first place).
>
> > # rc-update add net.eth1 default
>
> No - but deliberately.  I think this may be where I, or the system is
> confused.  Because unlike a desktop it's not just a matter of bringing
> up the /etc/init.d/net.* scripts.  I don't want DHCP timeouts etc. when
> booting off-line.

Not only that, but there's some automagic code in the rc scripts that will try 
to bring the interfaces up without linking it to a soft runlevel. So 
actually, you're better off not doing it. 
>
> net.eth0 is brought up by netplug

Actually the message is that net.eth0 is invoking netplug to wait for eth0 in 
the background. I could never work out why that doesn't work with net.eth1.

>
> net.eth1 is brought up by as I understand it, the ipw3945 module being
> loaded which runs the ipw3945 daemon, which runs wpa_supplicant, which
> runs the init script (maybe those last two steps are vice versa)
>
> So, currently:
> /etc/init.d/net.eth0 status
>  * status:  inactive
>
> (which is fine, the wire isn't plugged in)
>
> /etc/init.d/net.eth1 status
>  * status:  started
>
> which is fine, but I want sshd and ntpd to have recognised this
>
> In the end I want the services brought up when either or both of
> net.eth0 or net.eth1 are started (by cables being plugged in or wireless
> networks coming up etc.)
>
> Thanks for the response,
>
> W.

I guess what we both actually want is for these network dependent services to 
come up when *any* external network interface is functional. But how?


Regards,

Mike
-- 
gentoo-laptop@g.o mailing list


Replies:
Re: wireless and service dependencies
-- Will Briggs
References:
wireless and service dependencies
-- Will Briggs
Re: wireless and service dependencies
-- david
Re: wireless and service dependencies
-- Will Briggs
Navigation:
Lists: gentoo-laptop: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: wireless and service dependencies
Next by thread:
Re: wireless and service dependencies
Previous by date:
Re: wireless and service dependencies
Next by date:
Re: wireless and service dependencies


Updated Jun 17, 2009

Summary: Archive of the gentoo-laptop mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.