Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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 is launched with /usr/sbin/crond -l8 >>/var/log/cron 2>&1,
as Dillon says in his doc files.
I've a slackware 8.0 and i'm trying to test dillon's cron with:
crontab -e
* * * * * date >>/tmp/test
* * * * * date
:wq
I'm sure crond is running and accepting updates. In fact when I write ':wq' in crontab's vi the following happens:
1) /var/spool/cron/crontabs/cron.update is touched and contains 'root'
2) an empty /etc/crontab is touched
3) after a minute the two files are deleted
these things make me think cron is updating its jobs.
*But*
After all this:
1) /var/log/cron is empty (totally)
2) /tmp/test simply doesn't exists
3) this situation keeps itself inaltered in time
I really can't understand what's going on. Any hint would be *greatly* appreciated.
Is there an env variable $EDITOR? if so what its value? Another thing, what distribution is it? I remember there were questions about slack's interpretation of crontab and vi, if vi symlinked to elvis everuything works out, if it is an editor by itself strange things happen, I was able to fix them by explicitely exporting EDITOR variable set to vi
export EDITOR=/usr/bin/vi
I've checked your suggestion and found that everything is exactly as you say. Then I've changed the commands i put in crontab -e and amazingly it started to work.
I can only guess that for some reason unknown to me, the commands i formerly put in crontab -e did fail silently.
But as far as today crond keeps working, still I think its behavior is *strange*, considering that i had launched the daemon with debug level 0 but nevertheless it didn't log anything. Isn't it a lack of application performance?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.