Date: Tue, 01 Jul 2014 09:33:33 +0200 From: "Ronald Klop" <ronald-lists@klop.ws> To: cdr.nil@gmail.com, "Spil Oss" <spil.oss@gmail.com> Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-stable@freebsd.org Subject: Re: Hourly cron jobs running to early Message-ID: <op.xia5x7k0kndu52@ronaldradial.radialsg.local> In-Reply-To: <CAEJyAvPo-wrDhB0=N6u6FqW6pb9AJtdvpi31JnwFkUZYwB0fbQ@mail.gmail.com> References: <CAEJyAvNteTZA5xiUzwNr=W241LZzWMB%2BQppZa829eDDSsCT2ng@mail.gmail.com> <000f01cf9463$b1e0b300$15a21900$@gmail.com> <20140630131857.GL93733@kib.kiev.ua> <001201cf9484$e4e43a30$aeacae90$@gmail.com> <CAEJyAvPo-wrDhB0=N6u6FqW6pb9AJtdvpi31JnwFkUZYwB0fbQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Jun 2014 19:13:23 +0200, Spil Oss <spil.oss@gmail.com> wrote: > Sorry, forgot to mention that this is indeed i386... > > Applied the patch and it looks as though cron is behaving now Hi Spil, Didn't I suggest this fix to you about 3 weeks ago? http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2014-06/msg00104.html ;-) Cheers, Ronald. > > Before > Jun 30 18:58:59 gw /usr/sbin/cron[25911]: (root) CMD (/usr/libexec/atrun) > Jun 30 18:58:59 gw /usr/sbin/cron[25912]: (operator) CMD > (/usr/libexec/save-entropy) > > After > Jun 30 19:10:00 gw /usr/sbin/cron[26085]: (root) CMD (/usr/libexec/atrun) > Jun 30 19:11:00 gw /usr/sbin/cron[26097]: (operator) CMD > (/usr/libexec/save-entropy) > > Hourly will take a while... > > On Mon, Jun 30, 2014 at 7:01 PM, <cdr.nil@gmail.com> wrote: >> >>> -----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 >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "freebsd-stable-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.xia5x7k0kndu52>