cron not using new entry after crontab -e?
I just updated my cron to the one from frozen: 3.0pl1-55
I've noticed that when I do a crontab -e, even though cron says in the
logs that it sees the update, it doesn't run the new entry I put in
there.
When I take cron down, put in the entry, then bring it up, it sees it
fine.
I notice the new cron also installed a package called lockfile-progs,
which makes me suspicious.
Has anyone seen this, or should I file a bug report? I see a quite
similar bug reported 75 days ago, but no followup on the part of the
original filer to the developers' questions.
Reply to: