On Sunday 22 October 2006 13:24, Mike Frysinger wrote:
> all use this:
> > lo - net is up if lo is up
> > Just have net.lo in the boot runlevel - it should always be there anyway.
>
> so you're saying if net.lo is in the boot runlevel, and i put say net.eth0
> [wired] and net.eth1 [wireless] into my default runlevel, i dont have to
> worry about eth0/eth1 screwing up my net services ?
>
> for example, if i start stopping/starting net.eth[01], i certainly dont
> want sshd/tftpd/rsyncd/etc... starting and stopping as well ... nor do i
> want these services to fail because net.eth[01] failed to start at boot
>
> thus RC_STRICT_NET_CHECKING=lo gave me the perfect behavior

And by default you'll get that behaviour.
Infact we support none, lo and yes options without you having to set anything 
as that's all default :)

-- 
Roy Marples <[EMAIL PROTECTED]>
Gentoo/Linux/FreeBSD Developer (baselayout, networking)
-- 
[email protected] mailing list

Reply via email to