[Samba] Shutdown of nmbd process in SAMBA 2.2.3a

[MCCALL,DON (HP-USA,ex1)]

Hi Drew,
No, there is no parameter you can change for this.
nmbd is CODED to shut down if there are no interfaces to
listen on - it discovers this in a routine called
"reload_interfaces(t)"  which is called (along with other
things) after a sighup has been received, OR every 120
seconds (as defined by include/local.h:#define NMBD_INTERFACES_RELOAD
(120)).
So, bottom line, if this code happens to execute during your switch reboot,
causing nmbd to NOT find any interfaces, this behavior is expected.
You COULD minimize the window for this to happen by changing the code 
to make the NMBD_INTERFACES_RELOAD happen less frequently, but you could 
still hit it, of course.
I would hope that this switch reboot should be an infrequent thing, though,
and probably not worth this type of coding effort.
Hope this helps,
don

-----Original Message-----
From: Drew.Zeller at statcan.ca [mailto:Drew.Zeller at statcan.ca]
Sent: Thursday, April 04, 2002 9:29 AM
To: samba at lists.samba.org
Subject: [Samba] Shutdown of nmbd process in SAMBA 2.2.3a


Hi,

I am running SAMBA 2.2.3a on HP-UX 11.00.

Last night the network switch that my SAMBA servers is on was rebooted.  At
this same time the nmbd process on all my servers shutdown down.

In the /usr/local/samba/var/nmbd.log file on all my servers I found this
message :

[2002/04/03 20:39:28, 0] nmbd/nmbd.c:(259)
  reload_interfaces: No subnets to listen to. Shutting down...

Anyone have any ideas why the nmbd would shutdown when the network
connection was lost?  Is there a parameter that I can change for this?



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba