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,
i make local fix for this problem:
open smbd on all interface(0.0.0.0) and use internal(hosts allow) and external
protect
alternative: portforwarding onenVPN = 127.0.0.1 for smb working port on
iface-up may help for difficult situation(i think, restart deman is bad for
active users on other
** Changed in: openvpn (Ubuntu)
Status: New = Confirmed
** Changed in: openvpn (Ubuntu)
Importance: Undecided = Low
--
openvpn is started after samba (smbd, nmbd)
https://bugs.launchpad.net/bugs/613999
You received this bug notification because you are a member of Ubuntu
Server Team,
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
Associating to ifupdown because this is where the current net-device-up
signal is emitted, which is insufficient for network-aware services when
other services / jobs may in fact bring interfaces up.
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
** Changed in: samba
Associating to samba because nmbd is vulnerable to this problem.
--
openvpn is started after samba (smbd, nmbd)
https://bugs.launchpad.net/bugs/613999
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
