On Thu, May 11, 2006 at 11:37:20PM +0200, Jens Sülwald wrote: > Steve Langasek schrieb: > > On Thu, May 11, 2006 at 09:04:17AM +0200, Jens Suelwald wrote: > >> Samba segfaulted and sent a mail to me. A Client was connected using ssh to > >> forward the connection to another host.
> >> The Samba 'panic action' script, /usr/share/samba/panic-action,
> >> was called for pid 23332 (/usr/sbin/nmbd).
> >> Below is a backtrace for this process generated with gdb, which shows
> >> the state of the program at the time the error occurred.
> >> #4 0x080c31e4 in sig_fault (sig=-512) at lib/fault.c:42
> >> #5 <signal handler called>
> >> #6 find_workgroup_on_subnet (subrec=0x0, name=0x813b460 "ANIMANIACS")
> >> at nmbd/nmbd_workgroupdb.c:177
> >> #7 0x08076f64 in write_browse_list (t=0, force_write=1)
> >> at nmbd/nmbd_serverlistdb.c:350
> >> #8 0x0806267f in msg_reload_nmbd_services (msg_type=3001, src={pid = 0},
> >> buf=0xbffffcbc, len=0) at nmbd/nmbd.c:314
> >> #9 0x08062ef7 in main (argc=-1073746208, argv=0xbffffd44) at
> >> nmbd/nmbd.c:597
> > This failure in nmbd usually happens when you have an invalid interfaces
> > line in your smb.conf. Please post the interfaces line from
> > /etc/samba/smb.conf on this server.
> bind interfaces only = yes
> interfaces = 127.0.0.1
> these should be the lines you've requested.
Ok. This is a valid use of smbd, but it's not valid for nmbd. You'll want
to edit your /etc/init.d/samba script to not start nmbd in order to suppress
these mails, I guess, since you can never use nmbd in a configuration that
doesn't have broadcast interfaces.
--
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/
signature.asc
Description: Digital signature
