Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Oct 2012 09:10:17 -0700
From:      Maxim Sobolev <sobomax@FreeBSD.org>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        Ian Lepore <freebsd@damnhippie.dyndns.org>, Adrian Chadd <adrian@freebsd.org>, src-committers@freebsd.org, Garrett Cooper <yanegomi@gmail.com>, svn-src-all@freebsd.org, Pedro Giffuni <pfg@freebsd.org>, Bruce Evans <brde@optusnet.com.au>, svn-src-head@freebsd.org, Xin Li <delphij@delphij.net>
Subject:   Re: svn commit: r241625 - head/usr.sbin/cron/cron
Message-ID:  <50856FE9.1020807@FreeBSD.org>
In-Reply-To: <20121017201811.GO35915@deviant.kiev.zoral.com.ua>
References:  <201210170044.q9H0iZHo055977@svn.freebsd.org> <20121017174814.GN35915@deviant.kiev.zoral.com.ua> <507F0FF8.3090602@FreeBSD.org> <20121017201811.GO35915@deviant.kiev.zoral.com.ua>

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

The latest version of the patch against current HEAD is available here:

http://sobomax.sippysoft.com/cron.diff

Any comments/suggestions are appreciated. This version should default to 
previous behaviour of waking up every 60 seconds unless there is 
@every_second entry in the cron.

Konstantin, can you please put it for testing to your boxes? Please make 
sure to do `make clean' after applying it, as libcron is not listed as a 
dependency for cron, so it's possible that some changes may not be 
picked up.

Thanks!

-Maxim

On 10/17/2012 1:18 PM, Konstantin Belousov wrote:
> On Wed, Oct 17, 2012 at 01:07:20PM -0700, Maxim Sobolev wrote:
>> On 10/17/2012 10:48 AM, Konstantin Belousov wrote:
>>> The cron daemon in HEAD is not functional, i.e. no jobs are executed
>>> at all. Reverting r241625 r241618 r241576 gives me the expected behaviour.
>>>
>>> P.S. I do not remember a single commit from you which did not failed on
>>> tinderbox, or was not found buggy later.
>>
>> Should be fixed already in the latest HEAD. Please check and let me know
>> if you still have some issues (send crontab entry which is not getting
>> executed). The particular issue has been fixed in the r241618.
>
> Well, as I noted above, I had r241618 applied, since I needed to revert it.
> For me, neither the standard entries from /etc/crontab, nor the following
> user crontab:
> * * * * *       /usr/bin/limits -a >/tmp/1.txt
> are not executing. In particular, the /tmp/1.txt file was not created,
> and the cron.log was empty.
>
> As I said, a reversal of all three commits makes the cron(8) operate
> correctly.
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50856FE9.1020807>