Bug 7060 - nmbd does not start if no network interfaces up
Summary: nmbd does not start if no network interfaces up
Status: RESOLVED DUPLICATE of bug 13559
Alias: None
Product: Samba 3.4
Classification: Unclassified
Component: Nmbd (show other bugs)
Version: 3.4.2
Hardware: Other Linux
: P3 normal
Target Milestone: ---
Assignee: Jeremy Allison
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-25 12:50 UTC by Orion Poplawski
Modified: 2024-01-11 14:21 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Orion Poplawski 2010-01-25 12:50:33 UTC 
Current linux distros (Fedora 12 for e.g.) can start nmbd before the network interfaces are configured.  Currently, nmbd will exit if no interfaces are configured.  It would be very helpful if it stayed up and added/removed interfaces as they became available.
Comment 1 Andreas Hasenack 2017-10-30 13:41:19 UTC 
I believe this is fixed already, at least in samba4.

nmbd actually starts as usual, detects there is no network, and waits for the network *forever*: there is no timeout. Its loop is essentially this:
    while (iface_count_v4_nl() == 0) {
        sleep(5);
        load_interfaces();
    }

That's when it logs the message "No local IPv4 non-loopback interfaces available, waiting for interface...". It really waits forever.

What is happening nowadays, though, is that systemd is waiting for an sd_notify() from nmbd, and if that doesn't come in time, systemd will kill nmbd (!). You end up with a system where smbd is running, but nmbd was killed unnecessarily.
Comment 2 Björn Jacke 2024-01-11 14:21:23 UTC 

*** This bug has been marked as a duplicate of bug 13559 ***