Josip Rodin wrote: > I don't think the OP's bug is any different. He could have corrected the > error e.g. by what I did - by moving a backup file into place, but then > crond didn't pick up the 'new' file because it wasn't really new.
It doesn't have to be new in a chronological sense. The sole criterion for a re-scan is differing mtimes, which means moving an old backup over the broken crontab would trigger a re-scan. Please have a look at my initial response to the OP (message #25). If your crontab does not get re-scanned after following a) - e), you indeed have that bug. I would quite welcome that, because I haven't heard back from the OP yet, and I'd like to get this issue resolved. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
