From owner-freebsd-questions Sun Sep 19 21:18:38 1999 Delivered-To: freebsd-questions@freebsd.org Received: from earth.wnm.net (earth.wnm.net [208.246.240.243]) by hub.freebsd.org (Postfix) with ESMTP id 076A01506A for ; Sun, 19 Sep 1999 21:18:35 -0700 (PDT) (envelope-from alex@wnm.net) Received: from localhost (alex@localhost) by earth.wnm.net (8.8.8/8.8.8) with ESMTP id XAA17435; Sun, 19 Sep 1999 23:14:21 -0500 (CDT) Date: Sun, 19 Sep 1999 23:14:21 -0500 (CDT) From: Alex Charalabidis To: Jamie Norwood Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Weird cron actions In-Reply-To: <199909200220.WAA01700@cc942873-a.ewndsr1.nj.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Sep 1999, Crist J. Clark wrote: > Jamie Norwood wrote, > > Daily, I get a script running way early: > > > > 57 23 * * * $HOME/bin/tartoday.sh >> /dev/null > > > > I also note the security scripts run at 7pm rather than midnight? > > You mean it's running at 7 PM rather than 2 AM, right? > I'll assume the same. Some cron'ed tasks appear to be more confused than others when the CMOS clock != local time. This includes the default newsyslog in /etc/crontab which without fail runs at 1900 CDT on my machines (and I bet it'll start running at 1800 CST soon). This may warrant a PR. Maybe one of the resident kernel hackers can enlighten us a bit more regarding this odd behaviour. I might venture a wild guess and speculate that it has something to do with adjkerntz(8) but don't take my word for it 8). > head -1 /var/log/maillog Sep 19 19:00:00 dreamtime newsyslog[14077]: logfile turned over > grep newsyslog /etc/crontab 0 * * * * root newsyslog > It looks like your machine is a bit confused about whether it is > running with system clock at local time or UTC. > Agreed. My CMOS clock is set to UTC and the same thing happens both on 3.2-S and 3.3-RC. Still, my security scripts kick in punctually at 0200, so your setup may be a bit more messed up. I suggest you check the CMOS time and then enter sysinstall and make sure you've made the right choice in the time zone configuration section. I wouldn't be surprised if simply setting your CMOS clock to local time solved your problem once and for all. -ac -- Alex Charalabidis WebNet Memphis (901) 432-6000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message