Well, this design is wrong then, because I'm talking about /etc/crontab ,not about /etc/cron.d directory. System crontab ( /etc/crontab ) is protected by access rights, so it can't be changed by malicious user. And any error causes cron almost stop working, because in my case /etc/crontab contains all jobs. So , if malicious user has access to it he can stop cron from working, and, thus, stop mailing access reports to me, this is security hole :-)
I.e. this is not implementation bug, but design bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821566 Title: cron ignores whole crontab if one line has error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1821566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
