Red Hat Bugzilla – Bug 235932
ORPHAN (no passwd entry) in 4.1-80
Last modified: 2007-11-30 17:12:01 EST
Description of problem: Latest update broke vixie-cron for me including all cron-jobs: Apr 10 22:36:17 tux crond[1419]: (CRON) STARTUP (V5.0) Apr 10 22:36:17 tux crond[1419]: (mailget) ORPHAN (no passwd entry) Apr 10 22:36:17 tux crond[1419]: (sa-update) ORPHAN (no passwd entry) [...] Apr 10 22:40:01 tux crond[3530]: (vnstat) CMD (/usr/sbin/vnstat.cron) Apr 10 22:40:01 tux crond[3531]: (vnstat) CMD (vnstat /usr/sbin/vnstat.cron) --- snipp --- From: Cron Daemon <root@localhost> To: root@localhost Subject: Cron <vnstat@hurricane> vnstat /usr/sbin/vnstat.cron Unknown arg "/usr/sbin/vnstat.cron". Use --help for help. --- snapp --- Version-Release number of selected component (if applicable): vixie-cron-4.1-80 How reproducible: Everytime, see above. Expected results: Working stuff like in 4.1-78 ;-) Additional info: Vixie-cron was built without PAM support, but this shouldn't make any difference, shouldn't it?
PAM doesn't matter. Where have you your jobs? In /etc/cron.d or did you do them using crontab? I have also the ORPHANs in log, but the jobs are runned. My jobs are orphans only when they come from /etc/cron.d, jobs made by crontab run normally.
/etc/cron.d/vnstat (from vnstat package)
Fixed in vixie-cron-4.1-82.fc7