I just wanted to add what I know.
On a Celeron D 2.53, 650i, 4 GB, I did not have this issue, or at least I
didn't notice it.
When I switched over to AMD X2 4800+, 780G, 2 GB, I began to experience this
issue.
For what it's worth, if I reboot warm, the issue only occurs about half the
time.
If I reboot from cold (power off and or AC all the way off), it reproduces
itself reliably.
The 0.0.0.0 address listed in the log someone provided earlier looks like a
clue.
So just for fun I set the network from DHCP to Manual fixed static IP, and now
several
totally cold boots later, nmbd runs OK all by itself without needing anyone to
hold its hand.
It's not a perfect solution, especially if you have lots of PCs to
manage, but for me it's fine.
My guess is that on a faster CPU maybe with multiple cores, there is a
serialization issue
where nmbd gives up just before DHCP has successfully set the IP address. I'm
just guessing
based on the single-core machine not really having this issue.
Thanks, btw, for the great OS, I shall not ever buy windoze again.
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
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
