Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Jun 2014 10:34:14 +0100
From:      krad <kraduk@gmail.com>
To:        Ronald Klop <ronald-lists@klop.ws>
Cc:        freebsd-stable <freebsd-stable@freebsd.org>
Subject:   Re: cron jobs running early in virtual machine
Message-ID:  <CALfReyeaXkWu%2BPVRH8KBsMkBoHZC28VSgGFFYt2g4bJK=reGMQ@mail.gmail.com>
In-Reply-To: <op.xhadv0oakndu52@82-171-231-144.ip.telfort.nl>
References:  <CAEJyAvNm17i%2Bwt8d6yvs9BcEdBZyyEbVuaBBjydE7WyuC0Q2uA@mail.gmail.com> <op.xhadv0oakndu52@82-171-231-144.ip.telfort.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
it says its for 32bit boxes, so odd on hes 64 bit so most likely not.

Run a date on the host just before you run the date in the jail and compare
if you havent already


On 11 June 2014 11:53, Ronald Klop <ronald-lists@klop.ws> wrote:

> On Wed, 11 Jun 2014 11:31:02 +0200, Spil Oss <spil.oss@gmail.com> wrote:
>
>  Hi,
>>
>> I have a FreeBSD 10 running in VMWare ESXi 5.5. ntp is properly
>> configured and the time on the server is fine.
>>
>> What I've found is that cron jobs start early. I call newsyslog -v in
>> jails from the system crontab
>> in /etc/crontab
>> 0       0       *       *       *       root    jx all newsyslog -v
>>
>> jx is a simple wrapper to call that program in a named jail or 'all'
>> jails from jls
>> results in
>> Date: Tue, 10 Jun 2014 23:59:08 +0200
>> Subject: Cron <root@gw> jx all newsyslog -v
>> X-Cron-Env: <SHELL=/bin/sh>
>> X-Cron-Env: <PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin>
>> X-Cron-Env: <HOME=/root>
>> X-Cron-Env: <LOGNAME=root>
>> X-Cron-Env: <USER=root>
>>
>> Jail: build
>> Processing /etc/newsyslog.conf
>> /var/log/daily.log <7>: --> will trim at Wed Jun 11 00:00:00 2014
>>
>> So this will never cycle daily.log
>>
>> What can cause cron to start all jobs early? I tested this with a
>> simple `date' in cron as well and that's early too
>>
>> Kind regards,
>>
>> Spil
>>
>
> http://svnweb.freebsd.org/base?view=revision&revision=261231
>
> This was committed to stable/10 after 10.0-RELEASE. Maybe it has something
> to do with it.
>
> NB: I'm am not the author of the patch so I might be totally wrong.
>
> Ronald.
>
> _______________________________________________
> 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?CALfReyeaXkWu%2BPVRH8KBsMkBoHZC28VSgGFFYt2g4bJK=reGMQ>