Bug#79037: cron does not shout when the crontab lacks a newline.

2010-04-19 Thread Christian Kastner
(Jakub bounced, so I dropped him from CC:) Christian Kastner wrote: > Jakub Chmielewski wrote: >> I put some files in /etc/cron.d but have found out that the cron does not >> run then, though >> they are marked as loaded (RELOAD in the log). I've dug the source and found >> the load_user >> ro

Bug#79037: cron does not shout when the crontab lacks a newline.

2010-04-15 Thread Christian Kastner
unmerge 79037 tag 79037 -fixed thanks Hi Jakub, Justin, Jakub Chmielewski wrote: > I put some files in /etc/cron.d but have found out that the cron does not run > then, though > they are marked as loaded (RELOAD in the log). I've dug the source and found > the load_user > routine in user.c. W

Bug#79037: this bug/#79037 - cron does not shout when the crontab lacks a newline.

2008-03-31 Thread Justin Pryzby
* Warns when an error occurs parsing a user crontab (See: #79037). * user.c: Drop dead code path. It's unclear how to elegantly handle this during editing (crontab.c); at that point, it should effect a (specific) warning and prompt about "retry the same edit?". diff -u cron-3.0pl1/entry.c cron-