On Fri, 2004-01-23 at 15:19, Mike Fedyk wrote:
> On Thu, Jan 22, 2004 at 03:02:59PM -0800, Mike Fedyk wrote:
> > On Thu, Jan 22, 2004 at 12:16:29PM -0800, Mike Fedyk wrote:
> > > I have a custom smb.conf file which I'm attaching, and have just added:
> > > 
> > > panic action = "/usr/share/samba/panic-action"
> > 
> > Well, I figured out it should have been
> > 
> > panic action = "/usr/share/samba/panic-action %d"
> 
> Got one! (This is after switching back to a 2.4 kernel -- I was on 2.6.1 for
> the last week or so, and that was the entire time I had the debugging
> version of samba runing too, so there's some kind of "child exiting before
> parent notification" that is happening in 2.6)
> 
> Hmm, do I need to compile my libc non-stripped, or is the problem in
> tdb/tdb.c:1498?
> 

It's not there.  it's somewhere else - set MALLOC_CHECK_=2 into your
environment, and restart Samba.  This should help find out who did it.  

Grab current CVS to get samba to handle the backtrace from an abort(),
or just run the whole thing under valgrind :-)

Andrew Bartlett

-- 
Andrew Bartlett                                 [EMAIL PROTECTED]
Manager, Authentication Subsystems, Samba Team  [EMAIL PROTECTED]
Student Network Administrator, Hawker College   [EMAIL PROTECTED]
http://samba.org     http://build.samba.org     http://hawkerc.net

Attachment: signature.asc
Description: This is a digitally signed message part

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

Reply via email to