-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/06/2011 10:36 AM, Stefan Seyfried wrote:
Am Mon, 6 Jun 2011 10:15:39 +0200 schrieb Vitezslav Cizek <vcizek@suse.cz>:
The old cron manual said: "If the uid of the owner is 0 (root), he can put a "-" as first character of a crontab entry. This will prevent cron from writing a syslog message about this command getting executed."
But as you say, it worked even for unprivileged users' crontabs. (Probably a bug in old cron).
As I see it, The current cronie behaviour is correct.
Well. I would argue that "correct" in this case would be to not disable logging, but to still execute the command. Principle of least surprise. Maybe additionally log a warning that this is going to no longer work in after dec 31 2020 or something like that.
Crontabs not working after upgrade which did work fine before is IMHO nothing I'd call "correct".
Agreed. This is really the only approach that would make cronie an acceptable replacement. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk3uF5IACgkQLPWxlyuTD7IhZACgj79xfHeID0ERIjU2Bf9W7ti8 o3wAnjeTHta492PirFgTzEOBr49rZqCa =eSiP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org