Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I want a script (bash/zsh/ruby/...) to run at boot time in OS X. What's the most simple way to do this, without messing with xml/plist files, and preferably not needing to make a meta AppleScript.

share|improve this question

4 Answers 4

up vote 3 down vote accepted

MacOS X uses Vixie cron, which has special meta tags for launching at reboot time. See the man page for the file format.

something like:

@reboot /path/to/script.sh

in your crontab would work. I'm not sure that this a better solution than launchd, you probably have more meta tools that look at launchd than cron.

share|improve this answer
    
Love it, you proved me wrong :-) Although cron on OS X is not that great with logging by default (there was a topic on that just a few days ago). –  Daniel Beck Feb 14 '11 at 16:16
    
this is perfect. –  John Bachir Feb 14 '11 at 18:59
1  
Note that cron, at, and so on are to some extent deprecated in OS X. I can't find an explicit statement of that in the various docs, nor do I know how aggressively deprecated they are, but launchd does seem generally preferred. See the launchd documentation for an introduction. –  Norman Gray Feb 15 '11 at 18:55

In case you change your opinion:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>com.superuser.245713</string>
    <key>ProgramArguments</key>
    <array>
        <string>/path/to/script.sh</string>
    </array>
    <key>UserName</key>
    <string>someuser</string>
</dict>
</plist>

Store as com.superuser.245713.plist in /Library/LaunchAgents/ and make root:wheel the owner/group.

share|improve this answer
1  
It's arguably better to put it into /Library/LaunchAgents rather than /System/Library/LaunchDaemons since /System is OS-specific stuff and the one under /Library is used more for third party stuff. Also, LaunchDaemons "should contain items that will run as root, generally background processes" where as LaunchAgents "run as a user or in the context of userland". The source for those quotes is a great article on launchd that I consult for launchd questions. –  Doug Harris Feb 14 '11 at 16:19
    
@DougHarris Thanks for the suggestions! I have to admit I was just typing this ad-hoc -- while I usually test my solutions, I wasn't willing to restart my machine for this. –  Daniel Beck Feb 14 '11 at 16:22
    
This is very nice, although I like the Vixie cron solution better :) –  John Bachir Feb 14 '11 at 18:59
    
Actually, it should be put in /Library/LaunchDaemons. Agents only run inside a user session, i.e. they won't run (or more precisely, become eligible to run) until someone logs in, will run again every time someone logs in, and always run as the currently logged in user. Daemons run (/become eligible to run) at boot, and while they normally run as root, can be run as some other user with the UserName key. –  Gordon Davisson Apr 25 '12 at 4:56
1  
@the0ther The web doesn't forget. –  Daniel Beck Mar 24 at 21:23

There are also Login Hooks if you would prefer the script to run (as root) when a user logs in rather than when the machine is booted.

share|improve this answer

I just wrote an article on running a Bash script as root from boot. Don't forget the RunAtLoad command.

http://powercycled.wordpress.com/2012/04/25/spoof-mac-address-from-boot-using-launchd/

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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