Date: Thu, 16 Jan 1997 23:12:24 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: ponds!rivers@dg-rtp.dg.com (Thomas David Rivers) Cc: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: cron problems in 2.1.6.1 (not signaling crond of a change in a crontab.) Message-ID: <Mutt.19970116231224.j@uriah.heep.sax.de> In-Reply-To: <199701160314.WAA05440@lakes.water.net>; from Thomas David Rivers on Jan 15, 1997 22:14:43 -0500 References: <199701160314.WAA05440@lakes.water.net>
next in thread | previous in thread | raw e-mail | index | archive | help
As Thomas David Rivers wrote:
> My question is this: When a new crontab entry is installed in the
> system, should you have to do something to crond to get it recognized?
It should be picked up automatically based on the modification
timestamp of the crontab file:
u = find_user(old_db, fname);
if (u != NULL) {
/* if crontab has not changed since we last read it
* in, then we can just use our existing entry.
*/
if (u->mtime == statbuf->st_mtime) {
Debug(DLOAD, (" [no change, using old data]"))
unlink_user(old_db, u);
link_user(new_db, u);
goto next_crontab;
}
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970116231224.j>