Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Cron jobs must always be changed with "crontab -e", not by changing the conf file directly. What you found is the simple consequence of not following this rule. I suppose "crontab -e" is just a simple 3-step command: edit, check, apply (restart daemon).
Much the same way, sudo rules are changed with "visudo", not be changing the sudoers file directly.
But then, maybe you have a special need that makes you think you cannot use "crontab -e"? Non-interactive maybe?
If this is the case, consider tweaking the EDITOR environment variable instead.
Thanks for you replay, but I dont quite agree with you.
=> Cron jobs must always be changed with "crontab -e", not by changing the conf file directly. What you found is the simple consequence of not following this rule. I suppose "crontab -e" is just a simple 3-step command: edit, check, apply (restart daemon).
At least, you can supply a cron file directly to 'crontab', and after both 'crontab -e' and 'crontab CronFile', changes will take effect at once. There is no need to restart crond.
=> Much the same way, sudo rules are changed with "visudo", not be changing the sudoers file directly.
Personally speaking, there is no daemon running for sudo, does it mean the configuration file is read only when 'sudo' is used?
The difference between 'visudo' and 'vi' maybe that:
the first one will do a syntax check, but the seond will not.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.