You are not logged in.
zivziv wrote:dcron 4.4 executes cron.daily twice a day sometimes:
Hi thanks, I identified and fixed one bug that might be causing this. See
http://bbs.archlinux.org/viewtopic.php? … 47#p701047. The fix is in dcron-git now and will be in the next release.However, I am still surprised by the actual crond.log snippet you posted. There may well be another issue involved here.
If you have the time to follow the instructions at http://bbs.archlinux.org/viewtopic.php? … 77#p698877 and send me the debugging info, that would help me determine why you're seeing the behavior you are.
Thanks.
Hi.
I've sent you an e-mail containing required information.
Offline
Jim, a small feature request: Could we have the hostname somewhere in the subject line of cron-generated mails? This would help those of us who forward our mail from several servers to a central account.
Offline
I would like to make use of the "Nth day in the month" feature of dcron but am not having luck.
Today is Wednesday, March 17, 2010 (happy St Pat's!) the third Wednesday of the month. I added the following job with crontab.
* * 3 * wed echo "third wednesday of month" >> /tmp/cron.txt
The cron doesn't produce output. If I change the '3' to '*', it produces output as expected so the syntax in general should be fine. Here is debug info for the cron job:
User root Entry * * 3 * wed echo "third wednesday of month" >> /tmp/cron.txt
111111111111111111111111111111111111111111111111111111111111
111111111111111111111111
00010000000000000000000000000000
111111111111
0 0 0 1f 0 0 0
Command echo "third wednesday of month" >> /tmp/cron.txt
Am I misunderstanding how the Nth day of the month works?
Offline
Why does dcron have the environment variable LC_AL=C set and not default to the user's locale setting (eg en_CA.utf8)?
Offline
Because (1) it tries as much as possible to stay away from reading environment variables, this is part of its minimalist design; (2) I the current developer haven't yet been talked into making an exception for this. Recently I made one exception for the formatting of timestamps when logging to a file. If you want to make a case for more locale-sensitivity, I'll listen, but I don't promise in advance to do it.
At the moment, there's still some code cleanup and bugfixing waiting to be reviewed and pushed; I haven't been able to make development time for some weeks.
Offline
Hi Jim,
This is an FYI, in case you come across other users in this situation. The problem I had was with sort. Sort in a script ran from cron was producing different output than the same script run from the cli. I figured out it was because /etc/profile no longer has 'LC_COLLATE=C' set.
I have a new question for you. In the manpage of crontab(1) you have:
TODO
Ought to be able to have several crontab files for any given user, as an organizational tool.
Are you still planning to implement this feature? I took a look at your git repo but didn't see anything obvious. I'd like to make use of this feature otherwise I'll have to go to a plan B.
Lastly, thanks for your work on dcron. It's appreicated.
Offline
That was put on the TODO list by Matt Dillon, so it's been there a long time... I agree it'd be useful, but there's no prospect of it happening very soon, I'm afraid.
Offline
The shortcut has less fine-grained control over how often the retries happen, but it's probably good enough for your purposes. Specifically, a job like @daily will work as though it were FREQ=1d/Xm, where X minutes are 1/20th of a day (so, I think, 72 minutes).
I guess that is general? So @hourly would be FREQ=1h/3m ? What about @reboot? Do jobs that were set up via "HOUR DAY MONTH etc" get retried on EAGAIN as well?
My ship don't crash! She crashes, you crashed her!
Offline