Why do we need the “at” command in Linux?

I was studying code in which the at command is used. I looked around and found that it is used to execute batch jobs. It is used to schedule jobs. It is given, as its input, a command, and a time, relative or absolute.

So, my first question is: why is the at command used? Under which circumstances does one need to use at? I have encountered it when there was some bash script code trying to uninstall software and when some background services were to be restarted.

My second question: What is the difference between having any command executed as a batch job and having a command executed in calling command directly (or in subshell)?


Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

Bernhard’s reply is correct: in multi-user systems, the ability to execute heavy programs at some ungodly hours of the night is especially convenient, for both the person submitting the job, and his coworkers. It is part of “playing nice”.

I did most of my Ph.D. computations this way, combining the script with the nice command which demoted the priority of my work whenever other people were keeping the machine busy, while leaving intact its ability to hog all the system resources at night.

I used the very same command to check whether my program was running, and to restart it if necessary.

Also, you should keep in mind that at was written way before screen, tmux, and so on, so that it was a simple way to have a detached shell, i.e., one that would not die once you logged off the system.

Lastly, you should also notice that it is different from cron, which also has been around for a long time. The difference lies in the fact that at is occasional, while cron, being so repetitive, is more suited for system jobs which really need to be executed forever at fixed intervals: in fact, at gives you your own environment, with your own settings (and choices) of environment variable, while cron uses a minimal set of environment variables (just check the difference in PATH, as an example).

Method 2

I use the at command when I need to do some heavy processing on data, which I want to have executed during the night, when I am not behind my computer. Of course I could start the process just after I leave, but this is something I tend to forget.

The result of the command is not different from regularly execution of the script or command.

Method 3

When you have questions such as this always consult the man pages. They can be very enlightening.

What it does

excerpt from at man page

       at, batch, atq, atrm - queue, examine or delete jobs for later execution

       at  and  batch  read  commands  from  standard  input or a specified file
       which are to be executed at a later time, using /bin/sh.


The usage of the tools:

Usage: at [-V] [-q x] [-f file] [-mldbv] timespec ...
       at [-V] [-q x] [-f file] [-mldbv] -t time
       at -c job ...
       atq [-V] [-q x]
       atrm [-V] job ...

at includes 4 commands (at, atq, atrm, and batch). You use at and batch to schedule the jobs, atq to see what’s scheduled, and atrm to remove a job prior to it running.
$ at -f <cmd> timspec


The time to run the at job can be specified in different ways.

excerpt form at man page

At allows fairly complex time specifications, extending the POSIX.2
standard. It accepts times of the form HH:MM to run a job at a
specific time of day. (If that time is already past, the next day is
assumed.) You may also specify mid‐ night, noon, or teatime (4pm) and
you can have a time-of-day suffixed with AM or PM for running in the
morning or the evening. You can also say what day the job will
be run, by giving a date in the form month-name day with an optional
year, or giving a date of the form MMDD[CC]YY, MM/DD/[CC]YY,
DD.MM.[CC]YY or [CC]YY-MM-DD. The specification of a date must
follow the specification of the time of day. You can also give times
like now + count time-units, where the time- units can be minutes,
hours, days, or weeks and you can tell at to run the job today by
suffixing the time with today and to run the job tomorrow by suffixing
the time with tomorrow.


Say you have this shell script.

$ cat mycrontest.sh

 echo "It is now $(date +%T) on $(date +%A)"

Sample run:
$ ./mycrontest.sh
It is now 18:37:42 on Friday

Sample at job submissions:
$ at -f mycrontest.sh  10pm tomorrow
job 14 at Sun Jul  8 22:00:00 2007

$ at -f mycrontest.sh 2:00 tuesday
job 15 at Tue Jul 10 02:00:00 2007

$ at -f mycrontest.sh 2:00 july 11
job 16 at Wed Jul 11 02:00:00 2007

$ at -f mycrontest.sh 2:00 next week
job 17 at Sat Jul 14 02:00:00 2007


Method 4

Your network administrator informs you that some maintenance will occur to your web servers starting at 7pm and finishing by 2am. You want to serve a maintenance notification beforehand, and you want maximum uptime from your system. Are you going to stay up all night, ready to run various commands, and then start it up again later? No, you’d want to use at to schedule these tasks, then go to bed / play skyrim and forget about it.

Method 5

You can execute batch jobs in UNIX / Linux using any one of the three commands — at, batch or cron.

Schedule an at job using specific date and time


    $ at time date
For example, to schedule a job at 11 am on May 20, use the following at command.

    $ at 11 am may 20

Method 6

at can also be a really handy way to fire off reminders. My current dev machine is running OSX, so at and the simple notify.bash that I cobbled together can be really helpful:

$ at 5pm
notify.bash -t 'Work is over' -m "Don't forget to rollback INT environment"
$ at now + 15 minutes
notify.bash -m 'Check tests' -l 'http://integration.example.com/jobs/XXXX'
$ at now + 10 minutes
notify.bash -m 'Check the fridge, pudding should be done!'



DEFAULT_TITLE='Hey! Listen!'

function args.help () {
    local error="$1"
    if [ "$error" ]; then
        echo >&2 "$error"
    cat >&2 <<EOF
Usage $0 <options>

Displays a message using an Applescript notification box


--title <text>    Sets the title, otherwise the default is used ("$DEFAULT_TITLE")
 -t     <text>    Alias for --title

--link  <url>     Add a button to open a link
 -l     <url>     Alias for --link

--body  <text>    Set the message body
 -m     <text>    Alias for --body

function args.verify-not-empty () {
    local value="$1"
    local varname="$2"

    if [ "$value" ]; then
        echo "$value"
    elif [ "$varname" ]; then
        args.help "$varname cannot handle an empty argument"
        exit 1
            "The programmer forgot to include context, something was empty which shouldn't have been, but I can't tell you much more than that. Sorry :("
        exit 1

function args.parse () {
    while [ "$1" ]
        case "$1" in
            '-t' | '--title')
                TITLE=$(args.verify-not-empty "$1" title)
            '-l' | '--link')
                LINK=$(args.verify-not-empty "$1" link)
            '-m' | '--body')
                if [[ "$1" = '-' ]]; then
                    MESSAGE=$(cat -)
                MESSAGE=$(args.verify-not-empty "$MESSAGE" body)
                args.help "Unrecognized argument: $1"
                exit 1
    if [[ ! "$MESSAGE" ]]; then
        args.help "Message body was not specified"
        exit 1

function message.display-no-link () {
    osascript > /dev/null <<EOF
tell application "Finder"
  display alert "$TITLE" ¬
          message "$MESSAGE" ¬
          buttons { "Acknowledge" } ¬
          default button "Acknowledge"
end tell

function message.display-with-link () {
    osascript > /dev/null <<EOF
tell application "Finder"
  display alert "$TITLE" ¬
          message "$MESSAGEnnClick 'Open Link' to go to $LINK" ¬
          buttons { "Acknowledge", "Open Link" } ¬
          default button "Open Link"
          set response to button returned of the result
          if response is "Open Link" then open location "$LINK"
end tell

function message.display () {
    if [ "$LINK" ]; then

args.parse "<a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="9bbfdb">[email protected]</a>"

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

0 0 votes
Article Rating
Notify of
Inline Feedbacks
View all comments