Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35285 - [fcron] /usr/sbin/run-cron: No such file or directory with run-parts
Attached to Project:
Community Packages
Opened by Green (The_Green_Arrow) - Tuesday, 14 May 2013, 20:28 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 16 May 2013, 18:12 GMT
Opened by Green (The_Green_Arrow) - Tuesday, 14 May 2013, 20:28 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 16 May 2013, 18:12 GMT
|
DetailsDescription:
Ever since I've upgraded to the latest version 3.1.2-4, I've got the following in my local mail : /bin/sh: /usr/sbin/run-cron: No such file or directory Job /usr/sbin/run-cron /etc/cron.hourly terminated (exit status: 127) (mailing output) Additional info: * 3.1.2-4 * root fcrontab contains : &nice(15),nolog(true),bootrun 01 * * * * /usr/bin/run-parts /etc/cron.hourly Steps to reproduce: upgrade to fcron 3.1.2-4 Does run-parts need to be fixed ? |
This task depends upon
Closed by Dave Reisner (falconindy)
Thursday, 16 May 2013, 18:12 GMT
Reason for closing: Not a bug
Additional comments about closing: WAI
Thursday, 16 May 2013, 18:12 GMT
Reason for closing: Not a bug
Additional comments about closing: WAI
Comment by Dave Reisner (falconindy) -
Thursday, 16 May 2013, 16:54 GMT
Works fine here. Sounds like your systab wasn't reloaded by fcron....
Comment by Green (The_Green_Arrow) -
Thursday, 16 May 2013, 18:10 GMT
You're right. I've just removed the systab and systab.orig file in /var/spool/fcron since I use the root crontab anyway. Thanks.