| View previous topic :: View next topic |
| Author |
Message |
zfarkas
n00b
Joined: 28 Jul 2005
Posts: 6
|
 Posted: Mon Jul 18, 2011 2:39 pm Post subject: net.wlan0 not recognised as service providing 'net' [solved] |
 |
|
Hi!
I have an eth0 (used at work) and a wlan0 (used at home) connection at my laptop. The problem is that seems like only net.eth0 provides the 'net' service:
| Code: | # rc-status default | grep net
net.eth0 [ inactive ]
net.wlan0 [ started ]
netmount [ scheduled ] |
When I try to start netmount:
| Code: | # /etc/init.d/netmount restart
* WARNING: netmount is scheduled to start when net.eth0 has started |
I would expect netmount to be started when net.wlan0 is started. I have the same problem with libvirtd, ntp-client and ntpd, so basically every service depending on net: even if I have a working wlan0 connection, they are not started.
Any hint?
Thanks,
Zoltan
Last edited by zfarkas on Mon Jul 18, 2011 4:58 pm; edited 1 time in total |
|
| Back to top |
|
 |
MotivatedTea
Apprentice
Joined: 06 Nov 2006
Posts: 269
Location: Toronto, Canada
|
| Posted: Mon Jul 18, 2011 4:44 pm Post subject: |
|
|
Check the "rc_depend_strict" setting in "/etc/rc.conf" and try setting it to "NO". After the OpenRC upgrade, my file had a comment explaining the setting:
| Code: | # Do we allow any started service in the runlevel to satisfy the dependency
# or do we want all of them regardless of state? For example, if net.eth0
# and net.eth1 are in the default runlevel then with rc_depend_strict="NO"
# both will be started, but services that depend on 'net' will work if either
# one comes up. With rc_depend_strict="YES" we would require them both to
# come up.
rc_depend_strict="NO" |
|
|
| Back to top |
|
|
zfarkas
n00b
Joined: 28 Jul 2005
Posts: 6
|
| Posted: Mon Jul 18, 2011 4:57 pm Post subject: |
|
|
| MotivatedTea wrote: | Check the "rc_depend_strict" setting in "/etc/rc.conf" and try setting it to "NO". After the OpenRC upgrade, my file had a comment explaining the setting:
| Code: | # Do we allow any started service in the runlevel to satisfy the dependency
# or do we want all of them regardless of state? For example, if net.eth0
# and net.eth1 are in the default runlevel then with rc_depend_strict="NO"
# both will be started, but services that depend on 'net' will work if either
# one comes up. With rc_depend_strict="YES" we would require them both to
# come up.
rc_depend_strict="NO" |
|
Yes, that solved the problem (just found this...  ) |
|
| Back to top |
|
|
|
Networking & Security
