1 .Id $Id: at.1.in,v 1.7 1997/03/13 00:15:13 ig25 Exp $
2 .TH AT 1 "Nov 1996" local "Linux Programmer's Manual"
4 at, batch, atq, atrm \- queue, examine or delete jobs for later execution
42 read commands from standard input or a specified file which are to
43 be executed at a later time, using
47 executes commands at a specified time.
50 lists the user's pending jobs, unless the user is the superuser; in that
51 case, everybody's jobs are listed.
57 executes commands when system load levels permit; in other words, when the load average
58 drops below @LOADAVG_MX@, or the value specified in the invocation of
62 allows fairly complex time
63 specifications, extending the POSIX.2 standard. It accepts times
66 to run a job at a specific time of day.
67 (If that time is already past, the next day is assumed.)
74 and you can have a time-of-day suffixed with
78 for running in the morning or the evening.
79 You can also say what day the job will be run,
80 by giving a date in the form
85 or giving a date of the form
91 The specification of a date
93 follow the specification of the time of day.
94 You can also give times like
99 where the time-units can be
107 to run the job today by suffixing the time with
109 and to run the job tomorrow by suffixing the time with
112 For example, to run a job at 4pm three days from now, you would do
114 to run a job at 10:00am on July 31, you would do
116 and to run a job at 1am tomorrow, you would do
119 The exact definition of the time specification can be found in
120 .IR @prefix@/doc/at/timespec .
123 .BR at " and " batch ,
124 commands are read from standard input or the file specified
128 The working directory, the environment (except for the variables
133 and the umask are retained from the time of invocation.
138 command invoked from a
140 shell will retain the current userid.
141 The user will be mailed standard error and standard output from his
143 Mail will be sent using the command
149 shell, the owner of the login shell will receive the mail.
151 The superuser may use these commands in any case.
152 For other users, permission to use at is determined by the files
155 .IR @ETCDIR@/at.deny .
159 exists, only usernames mentioned in it are allowed to use
166 is checked, every username not mentioned in it is then allowed
170 If neither exists, only the superuser is allowed use of at.
174 means that every user is allowed use these commands, this is the
175 default configuration.
179 prints the version number to standard error.
182 uses the specified queue.
183 A queue designation consists of a single letter; valid queue designations
194 queue is the default for
200 Queues with higher letters run with increased niceness. The special
201 queue "=" is reserved for jobs which are currently running.
203 If a job is submitted to a queue designated with an uppercase letter, it
204 is treated as if it had been submitted to batch at that time.
207 is given a specific queue, it will only show jobs pending in that queue.
210 Send mail to the user when the job has completed even if there was no
216 rather than standard input.
230 shows completed but not yet deleted jobs in the queue; otherwise
231 shows the time the job will be executed.
233 Times displayed will be in the format "1997-02-20 14:50" unless the
236 is set; then, it will be "Thu Feb 20 14:50:00 1996".
240 cats the jobs listed on the command line to standart output.
254 cron(1), nice(1), sh(1), umask(2), atd(8)
256 The correct operation of
258 for Linux depends on the presence of a
260 type directory mounted on
265 is not available or corrupted, or if the user is not logged on at the
268 is invoked, the mail is sent to the userid found
269 in the environment variable
271 If that is undefined or empty, the current userid is assumed.
276 as presently implemented are not suitable when users are competing for
278 If this is the case for your site, you might want to consider another
279 batch system, such as
282 At was mostly written by Thomas Koenig, ig25@rz.uni-karlsruhe.de.
OSDN Git Service
