Christian Perrier <[EMAIL PROTECTED]> wrote: > > 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?
Sorry for the ambiguity. By "all" I mean eth0, ath0, and ppp0, which on my system is all but lo. > > 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.... And - why does it fail to see the lo interface at times? Maybe there is some race condition where the lo interface is temporarily unavailable during suspend/resume and nmbd might be looking at just that time. Doesn't smbd have the same algorithm? It isn't going down. > I would anyway recommend you to properly shutdown samba when shtting > down your laptop's interfaces. That seems like a good workaround. I'll do that. > ..or add "127.0.0.1" to "interfaces" (I > suppose you're using "bind interfaces only = yes"). I don't quite follow. I currently have the following in /etc/network/interfaces: iface lo inet loopback Just out of educational curiosity, can you be more specific about how you would update interfaces? Also, where would I look for "bind interfaces only = yes"? It doesn't sound familiar so I'm probably running the default, whatever that is ;-). > Note that this > does not solve the bug per se.... No problem. The Debian BTS is a wonderful source of good workarounds to common problems (until they get fixed). -- Bill Wohler <[EMAIL PROTECTED]> http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian! If you're passed on the right, you're in the wrong lane. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
