Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
I am using Ubuntu 5.10, with a gnome desktop (Clearview?) Run Level is 2. I want to record the opera every Tuesday night so that I can listen to it later.
If I set up crontab like this:
02 20 * * 2 sound-recorder -c 1 -S 40:00 -f wav opera.wav
it works.
If I set up crontab like this:
02 20 * * 2 sound-recorder -c 1 -S 240:00 -f wav opera.wav
it never starts.
-S 240 minutes is a valid parameter for sound-recorder and works just fine from the command line. Why not from cron?
Take a look at /etc/syslog.conf to see where cron messages are routed. For example:
Quote:
cron.* /var/log/cron
This would indicate that the messages are in /var/log/cron. If you see no mention of cron in /etc/syslog.conf, then the cron messages are in the default destination, usually '/var/log/messages'.
OK, I installed Ubuntu 5.10 to check out what's going on. The cron entry in /etc/syslog.conf is commented out. Remove the '#' at the beginning of the line, and save the file.
Restart sysklogd to pick up the change:
/etc/init.d/sysklogd restart
Restart cron to verify logging has started:
/etc/init.d/cron restart
You should now see entries in /var/log/cron.log. Rerun your test and check for errors.
Thank you so much! I enabled the cron.log (that would have been so useful to know about when I started this project), rescheduled it for today and let it run.
Now it works. I just don't get it -- nothing has changed (and I did check and recheck everything before coming to this forum); nevertheless, I'm glad to have the log working so that I can see future mistakes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.