In "Samba core dumps.", David Gilbert <dgilbert@jaywon.pci.on.ca> wrote: 
> Yeah... I know... if I'm using Samba, then I must be using
> <censored>.  Anyways... when I run nmbd, I get a core dump.  Currently
> the core dump looks like this (My old Sun4/260 is grinding away
> producing a debugging executable as we speak):
> 
> #0  0x411e2d0 in fclose ()
> #1  0x18f34 in dump_names ()
> #2  0x185d8 in write_browse_list ()
> #3  0x3354 in process ()
> #4  0x3f2c in main ()
> 
> Has anyone looked into this?

I don't see this behaviour on my 3/110 using Samba 1.9.16p2, NetBSD
1.2_Beta.

Does this happen when you initially run smbd?  What config items do you
have that may be causing this?  What if you don't configure any
shares?


-- 
   //////////////////////////////////////////////////////////////////////
  //  Scott Ellis   //   sellis@gi.com   //   sellis@rohan.sdsu.edu   //
 //////////////////////////////////////////////////////////////////////
// WARNING: This signature warps  time and space in its vicinity    //