Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Jun 2014 18:01:10 +0100
From:      <cdr.nil@gmail.com>
To:        "'Konstantin Belousov'" <kostikbel@gmail.com>
Cc:        freebsd-stable@freebsd.org
Subject:   RE: Hourly cron jobs running to early
Message-ID:  <001201cf9484$e4e43a30$aeacae90$@gmail.com>
In-Reply-To: <20140630131857.GL93733@kib.kiev.ua>
References:  <CAEJyAvNteTZA5xiUzwNr=W241LZzWMB%2BQppZa829eDDSsCT2ng@mail.gmail.com> <000f01cf9463$b1e0b300$15a21900$@gmail.com> <20140630131857.GL93733@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help

> -----Original Message-----
> From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-
> stable@freebsd.org] On Behalf Of Konstantin Belousov
> Sent: 30 June 2014 14:19
> To: cdr.nil@gmail.com
> Cc: freebsd-stable@freebsd.org
> Subject: Re: Hourly cron jobs running to early
> 
> On Mon, Jun 30, 2014 at 02:03:31PM +0100, cdr.nil@gmail.com wrote:
> > Folks,
> >
> > I, too, am seeing a problem of cron running jobs a few seconds too
early.
> > This is on a Thinkpad T42 running:
> >
> > FreeBSD cobalt 10.0-RELEASE-p6 FreeBSD 10.0-RELEASE-p6 #3 r267829M: Wed
Jun
> > 25 07:41:33 BST 2014     root@cobalt:/usr/obj/usr/src/sys/GENERIC  i386
> >
> > BIOS clock is running UTC and is under ntpd control.
> >
> > I noticed this on a logging cron job that is supposed to run on the
hour.
> > These are the last few timings:
> >
> > 03:59:47
> > 04:59:12
> > 05:59:47
> > 06:59:47
> > 07:59:47
> > 08:59:47
> > 09:59:47
> > 10:59:47
> > 11:59:47
> > 12:59:47
> >
> The head r261146, merged to stable/10 as r261231, seems to be
> relevant.

Konstantin,

Thanks for the pointer.  I've applied the patch and cron seems to be
behaving itself.

-mark




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001201cf9484$e4e43a30$aeacae90$>