fquest at paz.bz
Sun Feb 5 04:42:23 UTC 2017
I have no issue with cron executing every minute; it does.
* * * * * works fine and
*/1 is redundant as * means every minute
No, the problem is that the specific utility, atrun determines to not
execute. For whatever reason. An examination of the cron log shows the
attempt,but the utility simply decides it does not qualify at that moment.
I thought it was the load level (which is a criteria) but it seems not.
Even running atrun from the command line fails to execute. But the jobs
do eventually start executing. One a minute. It's as tho the atrun
utility has a time period where it will not run. I can't figure out what
that is. Nothing jumped out when looking at the source code.
On 2017-02-04 8:34 PM, jungle boogie wrote:
> On 02/04/2017 08:03 PM, Gary Aitken wrote:
>> Don't know if this is critical or not, but man crontab(5) lists the
>> as one of the "special" entries:
>> @every_minute Run once a minute, "*/1 * * * *"
>> so maybe adding the "/1" will do the trick,
>> or use the string "@every_minute".
> Yep, the */1 is definitely needed.
> DDG can help with crons:
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions