--- David Nicol davidnicol@gmail.com wrote:
On Thu, 24 Mar 2005 06:25:07 -0800 (PST), Leo Mauler webgiant@yahoo.com wrote:
I haven't used cron much as a mostly home user of Linux. My main Linux machine doesn't change all that often to need to run many cron jobs.
for the occasional task, you might be better using "at" rather than "cron"
Especially since "at" is more like a VCR than "cron".
And apparently "at" is a lot easier to get going: I think I'm doing the cron thingy right and I can't get any jobs to run (not even "run ls every minute from 6pm to 7pm on any month, day of the month, or day of the week.").
And I always thought: the very simplest words Must be enough. When I say what things are like Everyone's heart must be torn to shreds. That you'll go down if you don't stand up for yourself Surely you see that.
-- Bertolt Brecht
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Thursday 24 March 2005 07:47 pm, Leo Mauler wrote:
And apparently "at" is a lot easier to get going: I think I'm doing the cron thingy right and I can't get any jobs to run (not even "run ls every minute from 6pm to 7pm on any month, day of the month, or day of the week.").
Even if you did, you wouldn't necessarily see any output unless you had mail working on the sytem - cron mails the output to the owner of the crontab.
I would suggest that first you get the command you want cron to run working from a shell file - sometimes there are tricky escapes required for arguments that aren't required on the command line - then make sure that you use crontab -e to create the file. Also, make sure cron is actually running (chkconfig or rc-status should tell you).
-
Jonathan Hutchins -
Leo Mauler