Date: Sat, 4 Feb 2017 20:42:08 -0800 From: Jim Pazarena <fquest@paz.bz> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: atrun utility Message-ID: <aad5eeaa-0273-3335-cd46-6dda5346d130@paz.bz>
next in thread | raw e-mail | index | archive | help
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. Jim 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 >> following >> 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: > https://duckduckgo.com/?q=cron+*%2F1+*+*+*+*&t=hc&ia=answer > >> Gary > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aad5eeaa-0273-3335-cd46-6dda5346d130>