Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was wondering which file I should place this bash command in so it will be run on startup.

# Start the MongoDB server
/Applications/MongoDB/bin/mongod --dbpath /usr/local/mongo/data --fork --logpath /usr/local/mongo/log

I have been scouring the net and think it is between ~/.bashrc, ~/profile, /etc/bashrc, /etc/profile or ~/.bash_profile. Although I have tried these and they seem to run on terminal startup not Mac startup. Am I missing a file?

share|improve this question
up vote 26 down vote accepted

Officially none of these. The Apple suggested way is to use launchd. A Gui to set this up is lingon

As for the files you mention the ones in the home directory ~/.bashrc, ~/profile, ~/.bash_profile are only started when you login via a terminal.

EDIT: The ones in /etc are run by the shell starting for all users before the one in home directory. bash manual

The Unix startup script involved /etc/rc* but for OSX just use the launchd stuff

share|improve this answer
So if my command is inserted in either of the files in /etc it should be run on bootup? Does it matter what one it is in? – Wolfy87 Jan 6 '11 at 11:45
/etc/bashrc and so on are run when you start a shell, just like ~/.bashrc - it's just that the former will be run whenever any user starts a shell, rather than just your user. – Scott Jan 6 '11 at 12:07
@Scott is correct I have corrected my answer – Mark Jan 6 '11 at 12:14
Okay, but I just can't work out how to use launchd, I tried making a plist file for my program but I have no idea how to run it or how to get it to run on boot. – Wolfy87 Jan 6 '11 at 12:27

To run a command on start up on OS X, you need to use launchd.

If you don't want to use Lingon, you need to create a launchd Property List. This is an XML file, so you can do it with your favourite text editor or alternatively you can use the Property List Editor that's installed with the Mac OS X Dev Tools. Create the following:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "">
<plist version="1.0">
    <string></string> <!-- org.mongodb.mongodb perhaps? -->





Save this in /Library/LaunchAgents/ (you will need an administrator account and/or sudo), then open a terminal and do:

sudo launchctl load /Library/LaunchAgents/

This will cause launchd to load the item which will cause it to start MongoDB on boot. As a bonus, launchd will monitor it and, if it exits for any reason, it will be re-started. To get rid of the item simply replace load in the above command with unload.

share|improve this answer
This page (…) lists a lot of things something launched by launchd should not do. If I want to run an arbitrary command at startup I may not have control of and the command may wind up doing those things. In addition, I may not want launchd to restart and item that stops because it's a one-off or handles re-launching on its own. What should I do in these cases? – Michael Nov 8 '13 at 22:17
@Scott, thank you. This is the most helpful answer I found on the internet. – geotavros Feb 10 '14 at 15:04
This will attempt to run the application every 10 seconds, which works well for services that don't die. If this is for a script that runs once punctually (in my case, messaging once Slack on reboot) add <key>LaunchOnlyOnce</key><true/> to the dict. – msanford Apr 12 at 17:17

Another simple solution from Stack Overflow: You can:

  • Start;
  • Select "Application";
  • Click "Show library" in the toolbar (if hidden);
  • Add "Run shell script" (from the Actions/Utilities);
  • Copy-and-paste your script into the window;
  • Test it;
  • Save it somewhere: a file called will be created);
  • Go to System Preferences → Accounts → Login items;
  • Add this newly-created app;

Log off, log back in, and you should be done. ;)

share|improve this answer
Tested and works and it does not require launchd cumbersome plist editing nor paid Lingon app. – Lukasz Oct 2 '12 at 8:13
It does, however, add about 1804k of boilerplate to your three line shellscript! – android.weasel Sep 16 '15 at 14:06

You will have to look at how launchd and launchctl work on MacOS. You could start by reading the man pages for both the commands. You could then look inside /Library/LaunchAgents/ and /Library/LaunchDaemons/ for examples of how to set up applications to load at different times through the launchctl interface.

Here's an example I found on Stack Overflow that might help you further.

share|improve this answer

To launch commands when logging in, you can do this:

  • Create a text file containing your commands (bash script):

    # Start the MongoDB server
    /Applications/MongoDB/bin/mongod --dbpath /usr/local/mongo/data --fork --logpath /usr/local/mongo/log
  • Save this file in ~/Library/Startup.cmd

  • You can test it by double-clicking the file in the Finder
  • Make it executable: chmod +x ~/Library/Startup.cmd
  • Add this file in System Preferences > Accounts > Login items
share|improve this answer

If you want an approach that will work on Linux & Mac OS X, a cron task should should be sufficient (edit your cron tasks by executing crontab -e):

@reboot /path/to/script


share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .