Summary: | net.wlan0 started (and not net.eth0) does not fullfill net dependency in init-scripts. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | klavs klavsen <kl> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 66472 |
Description
klavs klavsen
2004-04-27 01:29:43 UTC
I have the same problem. I have found a hard coded net.eth0 in /var/lib/init.d, but it is dynamicly created and I don't know where... Is net.eth0 in your default runlevel? Also, check the setting of RC_NET_STRICT_CHECKING in /etc/conf.d/rc as this controlls the behaviour you are seeing. Hi - RF_NET_STRICT_CHECKING was set to no (default) which should mean one net started is enough. I have the same problem with the fact that I use ifplugd (because eth0 is not always cabled, and Gentoo currently can't be told to "start eth0 if there's a cable - otherwise try wlan0" which is IMHO a big lack :( When I restart f.ex. slapd on my portable (or any other service that depends on net) it INSISTS on starting my net.wlan0 (as it is the only one set to be started upon boot - eth0 is handled by ifplugd). Problem is - when I'm using eth0 - my net.wlan0 is usually not up - and so I have to wait for that to timeout :( I'd like portage to resolve the dependency so EITHER net.eth0 or net.wlan0 resolves the dependency on net.. AFAIK this is a missing feature in Gentoo's init system. Perhaps the best way was to make ifplugd work with gentoo's init system - or make gentoos init handle the above mentioned "start this if this=true else try this". This may be fixed by bug #77839 - however you will need baselayout-1.11.8 (any -rx version included) to apply the patch Fixed by baselayout-1.11.9 |