openvpn is started after samba (smbd, nmbd)
Bug #613999 reported by
dzs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
openvpn (Ubuntu) |
Confirmed
|
Low
|
Unassigned | ||
samba (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Binary package hint: openvpn
After boot the smbd and nmbd services are not bound to the tap interface created by openvpn. I think this is because openvpn is started after samba, because after a
# service nmbd restart
# service smbd restart
everything works fine.
I saw the samba services were already converted to upstart jobs but openvpn was not yet. Probably the rc scripts are executed after or parallel to the other upstart jobs.
Changed in openvpn (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Low |
To post a comment you must log in.
Confirmed on maverick, this is a problem with /etc/init/smbd.conf using
start on local-filesystems
I have not tested this, but one work around may be to change this to
start on started rc
which will cause smbd to come up after all of the traditional init.d scripts have been started.
For the long term, services which create or change network topologies will need to be started as a group and then emit a signal that controls when network-aware services (like nmbd especially) are started.