Trouble getting a core dump from clamd

krad kraduk at googlemail.com
Tue Jan 19 17:10:06 UTC 2010


2010/1/19 Doug Poland <doug at polands.org>

> Hello,
>
> I'm running 7.2-RELEASE-p3 i386 and am having an issue getting a core
> dump from a program that is seg faulting.
>
> Last night, inexplicably, clamd started to seg fault.  I was trying to
> obtain a core dump for further analysis but no .core file can be
> found.
>
> I've tried the following in a tcsh:
>
> # sysctl -a | grep core
> kern.corefile: %N.core
> kern.nodump_coredump: 0
> kern.coredump: 1
> kern.sugid_coredump: 0
> debug.elf32_legacy_coredump: 0
>
> # set ulimit=-c
>
> # /usr/local/sbin/clamd /usr/local/etc/clamd.conf
> Segmentation fault
>
> # tail /var/log/messages
> Jan 19 10:16:19 hostname kernel: pid 42315 (clamd), uid 106: exited on
> signal 11
>
>
> But I get no .core file.  Suggestions?
>
>
>
> --
> Regards,
> Doug
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at freebsd.org"
>

set a path in the sysctl variable kern.corefile. WIll make the core file
easier to find if one is generated. Generally much tider as well then having
core files littered all over the system


More information about the freebsd-questions mailing list