Re: Trying to figure out at, atrun, atd, and friends.
Dale Scheetz wrote:
>
> I have been trying to figure out how at works by reading the man pages.
> This has provided some confusion, as the man pages are not internally
> consistent (there are options listed at the Synopsis that aren't addressed
> in the text), nor are they consistent with the usage message.
at <timespec>
command
command
anymore commands
etc
^D
This will make your 'at' job. timespec is quite flexible, like
now, now+4days, Tue 0200...
> More to the point, there is not indication of how to write a "job" entry,
> nor is there any clear indication of how at interfaces with cron, although
> there is every indication that the two are intimately connected. The
Cron runs 'at' on a periodic basis.
> /usr/doc/at directory has no content of value. (BTW, there is a
> distressing amount of useless information in /usr/doc. It was my
> impression that this directory would hold "additional" documentation and
> not just copyright notices and changes files. When there is a READ.me file
> in this directory, it is usually about installing or building the package,
> also mostly worthless to the user trying to make something of the gigantic
> pile of software we provide)
>
> Some pointers on at would be very much appreciated, but I would really
> like to see us begin to address documentation issues like this. Supplying
> me with pointers will surely help me, but will do little for the other
> users unless it makes it into the "core" documentation.
The 'normal' wat to create a cron job is with a crontab entry.
As yourself, run 'crontab -e' to open up the editor with your
crontab file in it. If you have none, it will be blank. You
will enter 6 fields. From memory, they are
min hour day mon dayofweek command-to-run
So, to create a job that will run at 0100 every sunday, you could use
0 1 * * 0 commandstring
days of the week start with Sun, which is 0
Tim
--
(work) sailer@bnl.gov / (home) tps@buoy.com - http://www.buoy.com/~tps
Madness takes its toll...
Please have exact change!
** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.**
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: