On Sat, 13 May 2006 12:16 am, Gerald (Jerry) Carter wrote: > James, > > This was your change right ?
Yup. It's deliberately not configurable so that we can always get *something* that might help with fault diagnosis. > Doug, I'm more interested in why winbindd is seg > faulting in the SAMBA_3_0 tree. Can you give me more > details? Agreed. Please let's get a backtrace at least: gdb `which winbindd` /path/to/core/file (gdb) where (quit) > Doug VanLeuven wrote: > > Sorry Jeff, been there, done that, if you'd read the whole post. > > > > > > Jeff Saxton wrote: > >> man ulimit > >> hint: ulimit -c This probably won't work because in fault.c we explicitly set the core size to 16MiM (IIRC). > >> > >> Doug VanLeuven wrote: > >>> Hi all, > >>> Is there anyway to limit the new core dumping panics? > >>> Can't find anything on it. (If I'd only looked in that ...) > >>> Was my mistake, but winbindd filled up an entire volume > >>> and froze out every process writing to that drive. You should only get 1 core file per daemon unless you have some system-specific core file naming facility enabled. If winbind is dumping core often it should always be in LOGBASE/cores/winbindd/core. > >>> I started it from a shell and my soft limit is > >>> already zero. (ulimit -S -c 0) > > ^^^^^^^^^^^^^^ > >>> > >>> FC4 2.6.16-1.2069 smp, gcc 4.0.2-8 > >>> samba 3.0.23pre2-SVN-build-15162 > >>> > >>> Regards, Doug > >>> > >> > > > > -- James Peach | [EMAIL PROTECTED] | SGI Australian Software Group I don't speak for SGI. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
