From: "Sina Bahram" <sbahram@nc.rr.com>
To: <speakup@braille.uwo.ca>
Subject: RE: Help with date and redhat 9
Date: Sun, 26 Oct 2003 20:25:33 -0500 [thread overview]
Message-ID: <000201c39c29$3c699350$6401a8c0@quantum> (raw)
In-Reply-To: <Pine.LNX.4.44.0310261927230.3756-100000@champion.sent.com>
Thanks so much, that's what I needed to know.
I appreciate it.
Take care,
Sina
No trees were destroyed in sending this message. However, a large number
of electrons were terribly inconvenienced.
-----Original Message-----
From: speakup-admin@braille.uwo.ca [mailto:speakup-admin@braille.uwo.ca]
On Behalf Of Chuck Hallenbeck
Sent: Sunday, October 26, 2003 7:38 PM
To: speakup@braille.uwo.ca
Subject: RE: Help with date and redhat 9
Okay, here is how to do crontab...
First, make sure your favorite editor is specified in an environment
variable called "EDITOR" and also in one called "VISUAL". When you run
crontab with the -e option it will invoke one or the other of those, I
forget which! I use "ed" in mine, but you might prefer another editor.
So now become root and do this:
crontab -e
Now you are your favorite editor, and you create a one line entry
consisting of five time specifiers and one command, all on one line. The
time specifiers are separated from each other by a space and might be an
asterisk. They are as follows:
specifier #1 is the minute, from 0 to 59.
specifier #2 is the hour, from 0 to 23
specifier #3 is the day of the month, from 1 to 31
specifier #4 is the month, from 1 to 12
specifier #5 is the day of the week, and I forget if this is 0 to 6 or 1
to 7.
So to execute a command say at half past seven every morning, you would
make the line look like this:
30 7 * * * the-command-goes-here
Be sure the 30 starts in column 1!
So what you must do is decide what time each day you want your command
to run, and make a line like the example. If 7:30 AM is not convenient,
pick another time and use the specifiers to say when.
It is a good idea to redirect output from your command to /dev/null,
otherwise you get email to root! Also, you have to supply the full path
to your command, since no path is in effect during the crontab
execution.
When you have done all that, just save your work and exit, and the rest
is automatic.
Hope this helps.
Chuck
--
The Moon is Waxing Crescent (3% of Full)
Get my public key from website, http://www.mhonline.net/~chuckh
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
my mutt shit itself Alex Snow
` Help with date and redhat 9 Sina Bahram
` Chuck Hallenbeck
` Gregory Nowak
` Sina Bahram
` Barry Pollock
` Sina Bahram
` Adam Myrow
` Sina Bahram
` Sina Bahram
` Chuck Hallenbeck
` Sina Bahram
` Chuck Hallenbeck
` Sina Bahram [this message]
` Chuck Hallenbeck
` Sina Bahram
` Alex Snow
` Sina Bahram
` Gregory Nowak
` Sina Bahram
` Alex Snow
` Alex Snow
` Sina Bahram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000201c39c29$3c699350$6401a8c0@quantum' \
--to=sbahram@nc.rr.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).