dccifd stabilty issues with 1.2.74

Leandro Santi lesanti@uolsinectis.com.ar
Tue Mar 29 14:08:32 UTC 2005


Cami, 2005-03-29:
> 
> 
> 
> Vernon Schryver wrote:
> >What about `kill -s 3 PID` or `kill -s 6 PID` or whatever is needed
> >to send a SIGQUIT, SIGILL, or SIGABRT?
> 
> Nope, neither of those (SIGQUIT, SIGILL, or SIGABRT) generates
> any core file.
> 
> >If none of those case a core-dump, has something been set to
> >disable core dumps for the UID that runs dccifd?
> 
> Hmrph.. Whats quite interesting is the following:
> 
> [spamwall11][/var/amavis]$ ./a
> Segmentation fault
> [spamwall11][/var/amavis]$ ulimit -aH
> core file size        (blocks, -c) unlimited
> [spamwall11][/var/amavis]$ ulimit -c unlimited
> [spamwall11][/var/amavis]$ ./a
> Segmentation fault (core dumped)
> 
> Even though -c was already set to unlimited, only upon
> resetting it for that user enabled it to dump core.

I think that the problem is the soft rlimit. Try ``ulimit -aS'' before
``ulimit -c unlimited''. My debian box turns of core dumps by setting 
the soft limit to zero, but lets unprivileged users raise it at will...

Leandro.



More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.