User Commands                                               at(1)

NAME
     at, batch - execute commands at a later time

SYNOPSIS
     at  [-c  | -k  | -s ]  [ -m ]  [ -f file ]  [ -q queuename ]
     -t time

     at  [-c  | -k  | -s ]  [ -m ]  [ -f file ]  [ -q queuename ]
     timespec ...

     at -l  [ -q queuename ]  [ at_job_id. ..  ]

     at -r at_job_id. ..

     batch

DESCRIPTION
  at
     The at  utility  reads  commands  from  standard  input  and
     groups them together as an at-job, to be executed at a later
     time.

     The at-job will be executed in a separate invocation of  the
     shell,  running in a separate process group with no control-
     ling  terminal,  except  that  the  environment   variables,
     current   working   directory,   file   creation  mask  (see
     umask(1)), and system  resource  limits  (for  sh   and  ksh
     only,  see ulimit(1)) in effect when the at  utility is exe-
     cuted will be retained and used when the at-job is executed.

[ MATERIAL DELETED FOR BREVITY ]

     Users are permitted to use at  and  batch   (see  below)  if
     their  name  appears  in the file /usr/lib/cron/at.allow. If
     that file does not exist, the file /usr/lib/cron/at.deny  is
     checked  to determine if the user should be denied access to
     at . If neither file exists, only a user with the             |
     solaris.jobs.user authorization is allowed to submit a job.   |*
     If only at.deny
     exists and is empty, global usage is permitted. The at.allow
     and at.deny files consist of one user name per line.

[ MATERIAL DELETED FOR BREVITY ]