From owner-freebsd-bugs Thu Feb 17 11:54: 1 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from oceana.nlanr.net (oceana.sdsc.edu [132.249.40.200]) by hub.freebsd.org (Postfix) with ESMTP id D051437B841 for ; Thu, 17 Feb 2000 11:53:56 -0800 (PST) (envelope-from tshansen@oceana.nlanr.net) Received: from localhost (tshansen@localhost) by oceana.nlanr.net (8.8.6/8.8.6) with SMTP id LAA20241; Thu, 17 Feb 2000 11:53:53 -0800 (PST) Date: Thu, 17 Feb 2000 11:53:53 -0800 (PST) From: Todd Hansen To: freebsd-bugs@freebsd.org Cc: ampstaff@nlanr.net Subject: A repeat of cron problems as described in bin/6004 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org WE are also experiencing the cron problems mentioned in bin/6004. We run aproximately 100 systems distributed around the united states and over a long period of time we notice that some of these systems lose cron jobs. cron is still running and it runs some of our jobs fine. We are using a 3.0-RELEASE system and we are not able to upgrade them all at will so we were wondering if this bug has been noted and fixed in later versions of cron or if it has not yet been fully determined. If it is still undetermined then we would be very interested in helping you to debug it. If there is a release of FreeBSD with this fix, all we need to know is which one and we will upgrade the cron on those systems. Thanks for your time. I am including some debugging info below. I was unsure wether to submit a new bug report or to send a message to freebsd-bugs since the problem has already been mentioned in the GNATS system. -todd Crontab: joule.nlanr.net.actmon> crontab -l # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/crontab.eTKvHXl788 installed on Fri Dec 31 11:14:06 1999) # (Cron version -- $Id: crontab.c,v 1.11 1997/09/15 06:39:15 charnier Exp $) # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/crontab.ZOyLKT3056 installed on Tue Oct 27 16:51:55 1998) # (Cron version -- $Id: crontab.c,v 1.6.2.3 1998/03/09 11:42:00 jkh Exp $) * * * * * cd $HOME/src/pinger/vBNS ; sleep `jot -r 1 1 15` ; ./docollector 0,10,20,30,40,50 * * * * cd $HOME/src/pinger/vBNS ; sleep `jot -r 1 1 15` ; nice ./dogentrace ; cd $HOME/src/pinger/ ; ./watchdog -ko -t 600 -w watchdog.file "./am_master -n 10 -w watchdog.file amp volt &" 10 2 * * * find $HOME/src/pinger/vBNS/data -type f -mtime +5 -exec rm {} \; uname output: joule.nlanr.net.actmon> uname -a FreeBSD joule.nlanr.net 3.0-RELEASE FreeBSD 3.0-RELEASE #0: Fri Jan 14 12:16:27 PST 2000 tshansen@joule.nlanr.net:/usr/src/sys/compile/AMP i386 joule.nlanr.net.actmon> When job is not being run, we still see this every time it should run: Feb 16 12:01:00 nai-a-odun CRON[4212]: (actmon) CMD () While this is occuring the other jobs still run fine: Feb 16 12:02:01 nai-a-odun CRON[4226]: (actmon) CMD (cd $HOME/src/pinger/vBNS ; sleep `jot -r 1 1 15` ; ./docollector) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message