Date: Tue, 19 Jan 1999 16:11:26 +0100 (CET) From: Konrad Heuer <kheuer@gwdu60.gwdg.de> To: cjclark@home.com Cc: FreeBSD Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Help Diagnosing cron Death Message-ID: <Pine.BSF.3.96.990119160500.13023A-100000@gwdu60.gwdg.de> In-Reply-To: <199901191456.JAA23972@cc942873-a.ewndsr1.nj.home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Jan 1999, Crist J. Clark wrote: > Any ideas what it might be? Any help on how to track this down? I'm > not an expert on interprocess communications, what is a signal 4 (a > quick look at 'man signal,' 'man kill,' the cron src, and > /usr/include/signal.h did not turn it up)? /usr/include/sys/signal.h contains the #define instructions for the signal numbers; signal 4 is caused by an illegal instruction. By default there should be a core dump cron.core of cron in / (?). Although cron is surely not compiled with `-g' one might get some useful information by using gdb. So I suggest something like: # gdb /usr/sbin/cron /cron.core (gdb) where (gdb) ... I don't know how much can be seen from that but you could try. Regards // // Konrad Heuer ____ ___ _______ // Gesellschaft für wissenschaftliche / __/______ ___ / _ )/ __/ _ \ // Datenverarbeitung mbH GÖttingen / _// __/ -_) -_) _ |\ \/ // / // Am Faßberg, D-37077 GÖttingen /_/ /_/ \__/\__/____/___/____/ // Deutschland (Germany) ----- The Power to Serve ----- // http://www.freebsd.org // kheuer@gwdu60.gwdg.de // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990119160500.13023A-100000>