I can reproduce this, but not every time. So a race condition might be involved.
Where does Samba log errors when it can't bind to a socket? /var/log/samba/log.smbd: [2010/03/18 10:06:11, 0] smbd/server.c:1069(main) smbd version 3.4.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 [2010/03/18 10:06:11, 0] printing/print_cups.c:103(cups_connect) Unable to connect to CUPS server localhost:631 - Connection refused [2010/03/18 10:06:11, 0] printing/print_cups.c:103(cups_connect) Unable to connect to CUPS server localhost:631 - Connection refused [2010/03/18 10:06:12, 1] smbd/process.c:756(smbd_sig_hup_handler) Reloading services after SIGHUP [2010/03/18 10:06:12, 0] printing/print_cups.c:103(cups_connect) Unable to connect to CUPS server localhost:631 - Connection refused [2010/03/18 10:06:12, 0] printing/print_cups.c:103(cups_connect) Unable to connect to CUPS server localhost:631 - Connection refused -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
