From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: speakup@braille.uwo.ca
Subject: Re: cron
Date: Tue, 17 Jun 2003 18:53:47 -0600 (Mountain Daylight Time) [thread overview]
Message-ID: <Pine.WNT.4.56.0306171851160.1552@merlin> (raw)
In-Reply-To: <Pine.BSF.4.56.0306170153580.72618@server1.shellworld.net>
Luke,
I made a mistake in my previous post. The man page for crontab (1) will show the format of the crontab file. Sorry about that guys.
--
Joseph C. Lininger
jbahm@pcdesk.net
On Tue, 17 Jun 2003, Luke Davis wrote:
> Interesting. Does the end of your contrab(1) manual page, give you a "see
> also", to another crontab page?
>
>
> On Tue, 17 Jun 2003, Joseph C. Lininger wrote:
>
> > Alex,
> > This is what I'm running as well. I'll give you a quick run down on how the crontab file works in this version of cron. You can also look this up in the manual by looking at the man page for crond. Don't look for crontab, as this will only give you the crontab program's page. There is no man page in section 5 for crontab for this version.
> >
> > First, to edit crontab you will need to issue this command:
> >
> > crontab -e
> >
> > Make sure you set the VISUAL (notice that it's all caps) environment variable to the path to the text editor you want to use. This is the editor crontab will spawn.
> >
> > The format of this file consists of several fields. basically, the line looks like this:
> >
> > <minute> <hour> <day> <month> <days of the week> <command>
> >
> > For any of these fields, you may use an absolute number, a list seperated by commas, or a * to indicate all values. Also, you can use a skip factor to have cron skip running the job at certin times. I'll show that in the examples below. For the <days of the week> field, you should use 0 for sunday through 6 for saturday. You'll want to direct the output of the command you run to /dev/null or some log file or you'll end up getting the results emailed to you.
> >
> > Ok, now a couple of examples.
> >
> > # run a command at 4:30 AM every day
> > 30 4 * * * somecommand
> > # run a command at 2:30 in the afternoon on the first of the month
> > 30 14 1 * * somecommand
> > # run a command at midnight every monday and tuesday
> > 0 0 * * 1,2 somecommand
> > # illistrates the skip factor--run a command every 15 minutes
> > */15 * * * * somecommand
> >
> > Ok, if you have any more questions, let me know.
> >
>
> _______________________________________________
> 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: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
cron Alex Snow
` cron Adam Myrow
` cron Alex Snow
` cron Ann Parsons
` cron Ralph W. Reid
` cron Alex Snow
` cron Thomas Stivers
` cron Joseph C. Lininger
` cron Alex Snow
` cron Joseph C. Lininger
` cron Luke Davis
` Joseph C. Lininger [this message]
` cron Alex Snow
` cron Luke Davis
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=Pine.WNT.4.56.0306171851160.1552@merlin \
--to=jbahm@pcdesk.net \
--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).