> Good question. Looking... > > In /var/log/samba: > > -rw-r--r-- 1 root root 486 2006-01-13 09:11 log.nmbd.1 > -rw-r--r-- 1 root root 0 2006-01-15 03:06 log.nmbd > > Here is the entire content of log.nmbd.1 (it's short, and filled for > readability): > > [2006/01/12 13:29:12, 0] nmbd/nmbd.c:main(717) > Netbios nameserver version 3.0.20b-Debian started. > Copyright Andrew Tridgell and the Samba Team 1992-2005 > [2006/01/12 13:35:03, 0] > nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) > ***** > > Samba name server OLGAS is now a local master browser for workgroup > WORKGROUP on subnet 192.168.0.104 > > ***** > [2006/01/13 09:11:11, 0] nmbd/nmbd.c:reload_interfaces(265) > reload_interfaces: No subnets to listen to. Shutting down... > > Note the time that the server was started and the time of my nmbd.pid > file are the same: > > [EMAIL PROTECTED]:1154]$ l /var/run/samba/nmbd.pid > -rw-r--r-- 1 root root 5 2006-01-12 13:29 /var/run/samba/nmbd.pid > > Given the time of the reload, I had probably suspended and resumed my > laptop. I bring down all the network interfaces on suspend in > anticipation of coming up on a new interface elsewhere.
including the "lo" interface? > > Looks like the reload_interfaces simply neglected to clean up after > itself. Yep, that seems to be the cause. nmbd regularly checks the interfaces it's listening to and shuts down when none is active. This raises two concerns, imho: -there could be an option for not doing so, maybe -why is nmbd not cleaning its PID file? Here this is not a crash, this is a "normal" shutdown of the process.... I would anyway recommend you to properly shutdown samba when shtting down your laptop's interfaces...or add "127.0.0.1" to "interfaces" (I suppose you're using "bind interfaces only = yes"). Note that this does not solve the bug per se.... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
