tags 433449 upstream thanks On Tue, Jul 17, 2007 at 10:12:48AM +0100, Sam Morris wrote: > My system's network connection is a wireless one, and whenever I bring > the interface down to change networks, or get the hardware's driver back > into an unconfused state (it's not the most stable piece of coding), > nmbd exits.
> [2007/07/17 09:00:19, 0] nmbd/nmbd.c:reload_interfaces(229) > reload_interfaces: No subnets to listen to. Shutting down... > It should just hang around, listening on localhost It doesn't do this because nmbd is of no use listening on localhost alone; the services it provides make no sense on a loopback interface. > and/or 0.0.0.0 (all interfaces) until another network interface comes > back up. I don't know why it doesn't do this, but this question has recently been raised on the upstream mailing list as well. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
