50

I am going to schedule a job by using at command. Here I tried the following command:

$ at now + 1 minute
echo 'Test at command'
<EOD>

I saw the job is scheduled by using at -l. However, I saw no echo out.

I guess that I may need to add user to at.allow file. I cannot find at.allow in my Mac (Snow Leopard). Not sure what I need to do to test this at command?

Improve this question
3
  • I tried to read info from man at. It mentioned that "If the file _PERM_PATH/at.allow exists, only usernames mentioned in it are allowed to use at... If ... at.allow does not exists, _PERM_PATH/at.deny is checked,.." I am not sure what _PERM_PATH is.
    – David.Chu.ca
    Sep 19, 2009 at 4:41
  • In the case of Apple OSX Leopard, PERM_PATH for "at" is /usr/lib/cron.
    – Richard Hoskins
    Sep 19, 2009 at 15:28
  • For Mac OS X Lion it's /var/at
    – Stefan Schmidt
    Oct 12, 2011 at 19:44

6 Answers 6

Reset to default
47

To enable the needed atrun daemon, as man atrun says, execute:

launchctl load -w /System/Library/LaunchDaemons/com.apple.atrun.plist

as root (e.g. via sudo). Once you've done that, /var/at/ will be the key directory (though the simplest way is to use at as root -- e.g., once again, by sudo!-).

Improve this answer
8
  • I know that you need to be root to enable the atrun daemon, but you do not need to be root to run "at" commands. (Unless those commands require root.)
    – Richard Hoskins
    Sep 19, 2009 at 15:24
  • 1
    does this activation or atrun survive reboots?
    – Eric O. Lebigot
    Jun 30, 2011 at 9:38
  • According to the man page yes, but I haven't tried it.
    – Stefan Schmidt
    Oct 12, 2011 at 19:38
  • 1
    if /var/at/at.deny is empty you don't need to be root to queue at jobs, otherwise you can add your username to /var/at/at.allow.
    – Stefan Schmidt
    Oct 12, 2011 at 19:42
  • 6
    It's now May, 2019. This answer was correct for some older versions of macos, but it's not a complete answer for Mojave. There's a current, up-to-date answer on the U&L SE site.
    – Seamus
    May 30, 2019 at 11:08
15

In Snow Leopard you need to:

  1. Edit the /System/Library/LaunchDaemons/com.apple.atrun.plist, change the disabled child node from true -> false.

  2. Unload the current /System/Library/LaunchDaemons/com.apple.atrun.plist with:

    sudo launchctl unload -F /System/Library/LaunchDaemons/com.apple.atrun.plist

    Then load the edited version

    sudo launchctl load -F /System/Library/LaunchDaemons/com.apple.atrun.plist

  3. Test that it works with:

    echo blah | at now+1

  4. In case the echo fails for a different reason, you should be able to at least see the queue get cleared with:

    atq
Improve this answer
1
  • 1
    This is the only one that worked for me on OSX 10.10 Yosemite.
    – Colin Dean
    Nov 8, 2014 at 20:24
5

I tried this on OS X Lion and it seemed to work.

First enable the atrun deamon:

launchctl load -w
/System/Library/LaunchDaemons/com.apple.atrun.plist

Then add [your username] to /var/at/at.allow.

When executed you will receive output at /var/mail/[your username]

I find that queued items with batch take a few minutes to get actually get executed.

Improve this answer
3

Others have replied about at being disabled on Mac OS X, and I don't know about that, but there is another problem: Where do you expect your echo command to print its message? On other Unix systems that I have used it does not print in the same shell window where you gave the at command. Remember that when the at job is run, you might not even be logged in any more.

Try to write something to a file instead, and see if that file appears at the right time.

Improve this answer
2
  • The man page states, that the output will be mailed to you.
    – Stefan Schmidt
    Oct 12, 2011 at 19:39
  • 1
    @Stefan: Yes, and that worked well in the 1980's, when mail was handled locally on the same machine, but my experience (with other types of Unix than Mac OS X) is that nowadays you shouldn't expect to get any mail.
    – Thomas Padron-McCarthy
    Oct 13, 2011 at 3:04
2

The launchctl step wasn't enough for me; Seamus's comment pointed me to a more recent answer.

The TL;DR is you also need to add /usr/libexec/atrun at System Preferences > Security & Privacy > Full Disk Access.

Improve this answer
0

My installation of OS X (10.4) says in man at:

NOTE
     at, batch, atq, atrm are all disabled by default on Mac OS X.

Have you enabled atrun according to the instructions there?

Improve this answer
1
  • I tried to find where is atrun in my Mac. From web, another option is to add user to at.allow. I could not find this file (at.allow) neither.
    – David.Chu.ca
    Sep 19, 2009 at 4:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.