Ask Different is a question and answer site for power users of Apple hardware and software. 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 created the /etc/launchd.conf file but at start the content is never read.

The content of launchd.conf is: load /System/Library/LaunchDaemons/KillVuze.plist

(I run on OSX 10.7.2 )

If I load the plist by command line the "launchd list" show my plist as registered, but not after reboot even if I proper set the /etc/launchd.conf

Is this loading of non-default plist files (those stored outside the normal locations) best accomplished in this manner?

share|improve this question
Is there some reason you need to save the plist in /System/Library/LaunchDaemons/? Ones in ~/Library/LaunchAgents/ and /Library/LaunchAgents/ should get loaded automatically. – user495470 May 29 '12 at 16:46

To load a launchd job at start up, you need to store your job description plist file in one of two folders:

  • /Library/LaunchAgents
  • /Library/LaunchDaemons

Do not edit or store launchd job description files in the /System folder. This folder is reserved for exclusive use by Apple.

You do not need to edit any configuration files.

share|improve this answer

Your Answer


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.