Ok, after some discussion with Steve it appears this is unrelated to bug
#462169, and its only by mistake that /etc/network/if-up.d/samba is even
shipped.
It would appear that the currently supported way to bind samba to a
specific interface is to also change /etc/init/smbd.conf to be
start on (local-filesystems and net-device-up IFACE=ethX)
So that you can guarantee that it does not start until that specific
interface is up and ready.
Another option is to use
interfaces = ethX
instead of binding to a specific IP, so that smbd will just poll that
inteface and "just work" when it does get an IP.
Either way, it seems that smbd is doing the right thing in your
situation, but your configuration isn't supportable in the generic
sense. So unless we're missing something, you probably just need to
change /etc/init/smbd.conf to wait for the specific interface.
Closing as Invalid. Please feel free to re-open it by changing the
status to New if you have more information, or open a new bug report if
you feel that this one does not capture your problem appropriately.
Thanks for the report as well!
** Changed in: samba (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/836849
Title:
Samba starts before static IPs set in network manager
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/836849/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
