Date: Sat, 14 Mar 1998 07:56:57 -0800 (PST) From: null.angel@null.angel.nu To: freebsd-gnats-submit@FreeBSD.ORG Subject: bin/6004: cron in -CURRENT sometimes fails to process cron jobs. Message-ID: <199803141556.HAA23027@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 6004 >Category: bin >Synopsis: cron in -CURRENT sometimes fails to process cron jobs. >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Mar 14 08:00:04 PST 1998 >Last-Modified: >Originator: Thomas Stromberg >Organization: RTCI, Inc. >Release: FreeBSD 3.0-CURRENT >Environment: FreeBSD nineveh.angel.nu 3.0-CURRENT FreeBSD 3.0-CURRENT #2: Fri Mar 13 12:20:39 GMT 1998 null.angel@nineveh.angel.nu:/usr/src/sys/compile/nebuchadazzar i386 >Description: When setting a cron job (via crontab -e), cron jobs would suddenly "stop" being executed. For instance: */1 * * * * /www/null.angel.nu/desktop/dumpme worked for 4 hours, and then suddenly stopped. It was still processed by cron, (as /var/cron/log would report every minute), but the job itself was never executed. This also occured with this entry: */1 * * * * /usr/X11R6/bin/xwd -display localhost:0.0 -out /tmp/dump.xwd -silent -root; /usr/local/bin/convert -quality 50 /tmp/dump.xwd /tmp/dump.jpg; >How-To-Repeat: >Fix: Unfortunatly, the only way I could get the jobs to execute again were to kill -9 the cron, and start it again. >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803141556.HAA23027>