Discussion:
fcrontab and fcrondyn reporting different commands
jboogie
2013-05-27 20:23:27 UTC
Permalink
Hi, I recently switched from cronie to fcron, and I have just a small
issue - I'm getting mails of unsuccessful attempts to run

/usr/sbin/run-cron /etc/cron.hourly/

from systab, and that's because in my system (Archlinux) that file is
non-existent, and instead I have "/usr/bin/run-cron". However, the
crontab for systab seems correct:

# fcrontab -u systab -l
2013-05-27 22:16:22 INFO listing systab's fcrontab
&bootrun 01 * * * * /usr/bin/run-cron /etc/cron.hourly
&bootrun 02 00 * * * /usr/bin/run-cron /etc/cron.daily
&bootrun 22 00 * * 0 /usr/bin/run-cron /etc/cron.weekly
&bootrun 42 00 1 * * /usr/bin/run-cron /etc/cron.monthly

but fcrondyn disagrees:

# fcrondyn -x "ls systab"
ID SCHEDULE CMD
12 05/27/2013 23:01 /usr/sbin/run-cron /etc/cron.hourly
11 05/28/2013 00:02 /usr/sbin/run-cron /etc/cron.daily
9 06/01/2013 00:42 /usr/sbin/run-cron /etc/cron.monthly
10 06/02/2013 00:22 /usr/sbin/run-cron /etc/cron.weekly

why is there this discrepancy? And how do I fix it properly (i.e.
without symlinking)?

best regards,
renato
Thibault Godouet
2013-05-29 21:28:36 UTC
Permalink
Hi Renato,

That's strange... it may be best to do a "fcrontab -u systab -z" to
reinstall the fcrontab from the source (i.e. what you see with "fcrontab
-u systab -l").
Please note it will reset things for that fcrontab, e.g. it will be as
if it was a new one and the jobs had never run.

Regards,
Thibault.
Post by jboogie
Hi, I recently switched from cronie to fcron, and I have just a small
issue - I'm getting mails of unsuccessful attempts to run
/usr/sbin/run-cron /etc/cron.hourly/
from systab, and that's because in my system (Archlinux) that file is
non-existent, and instead I have "/usr/bin/run-cron". However, the
# fcrontab -u systab -l
2013-05-27 22:16:22 INFO listing systab's fcrontab
&bootrun 01 * * * * /usr/bin/run-cron /etc/cron.hourly
&bootrun 02 00 * * * /usr/bin/run-cron /etc/cron.daily
&bootrun 22 00 * * 0 /usr/bin/run-cron /etc/cron.weekly
&bootrun 42 00 1 * * /usr/bin/run-cron /etc/cron.monthly
# fcrondyn -x "ls systab"
ID SCHEDULE CMD
12 05/27/2013 23:01 /usr/sbin/run-cron /etc/cron.hourly
11 05/28/2013 00:02 /usr/sbin/run-cron /etc/cron.daily
9 06/01/2013 00:42 /usr/sbin/run-cron /etc/cron.monthly
10 06/02/2013 00:22 /usr/sbin/run-cron /etc/cron.weekly
why is there this discrepancy? And how do I fix it properly (i.e.
without symlinking)?
best regards,
renato
-------------------------------------------------------------------------------
- Fcron user support mailing list -
http://fcron.free.fr
*******
Liste de diffusion fcronsupport
jboogie
2013-05-30 18:26:28 UTC
Permalink
On Wed, 29 May 2013 22:28:36 +0100
Post by Thibault Godouet
Hi Renato,
That's strange... it may be best to do a "fcrontab -u systab -z" to
reinstall the fcrontab from the source (i.e. what you see with
"fcrontab -u systab -l").
Please note it will reset things for that fcrontab, e.g. it will be
as if it was a new one and the jobs had never run.
thanks, that worked.

cheers,
renato

Loading...