I have openafs installed, kernel module as well. I am accessing network via eth0 (ethernet connection) or wlan. When working via eth0, the service starts during boot without any problem. When no eth0 connection is available, but wifi connection is, the service does not start correctly. Instead I get following message: * WARNING: openafs-client is scheduled to start when net.eth0 has started the list does not contain net.wlan0, which is a primary adapter when using wifi connection. the whole problem disappeared when I removed 'need net' command from openafs-client and openafs-server init scripts (/etc/init.d/) Reproducible: Always Steps to Reproduce: 1. configure eth and wifi connections 2. start wifi connection without cable inserted into eth 3. restart client: /etc/init.d/openafs-client restart Actual Results: poco luks # /etc/init.d/openafs-client restart * Caching service dependencies... [ ok ] * Stopping OpenAFS client... * Unmounting /afs... [ ok ] * Stopping OpenAFS daemon... [ ok ] * Unloading OpenAFS module... [ ok ] * WARNING: openafs-client is scheduled to start when net.eth0 has started Expected Results: openafs client correctly running The openafs application itself runs correctly when eth0 is found, or when 'need net' is removed from the scripts and service is restarted once the wifi connection is established.
Please post your "emerge --info". Re-open this bug when you provide the requested information.
Created attachment 184642 [details] emerge --info emerge --info
emerge --info added
It seems to me you are looking for the option RC_NET_STRICT_CHECKING in /etc/conf.d/rc, am I correct?