[Bug 613999] Re: openvpn is started after samba (smbd, nmbd)

[Stéphane Graber]

Mark as Invalid for ifupdown as I don't see what we can do here to help
that kind of corner case.

If this is indeed a common use case (and I doubt it's), it might be
worth updating samba to ship a job (or ifupdown hook) reloading the
service when a new interface is brought up.

Alternatively, once openvpn is ported to upstart (if that hasn't been
done yet), it should be possible for the system administrator to simply
add a condition to samba (and net-device-up=tap0 or similar).

** Changed in: ifupdown (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/613999

Title:
  openvpn is started after samba (smbd, nmbd)

Status in “ifupdown” package in Ubuntu:
  Invalid
Status in “openvpn” package in Ubuntu:
  Confirmed
Status in “samba” package in Ubuntu:
  Confirmed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/613999/+subscriptions