Is it possible to load non-default launchd plist files from the /etc configuration file

launchd

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?

Best Answer

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.

Related Solutions

MacOS – Derive the launchd config plist based on a launch label

locate com.spotify.webhelper should do the trick as long as the plist is properly named (and the update process for the locate db has at least run once since you installed Spotify). Otherwise have a look at /Library/LaunchAgents, /Library/LaunchDaemons and their equivalents in your own Library folder.

MacOS – Submitting job to launchd gives error “no plist returned”, “nothing found to load”

That error is usually shown when there is a syntax error when checking with plist command.

In this case:

label should be Label,

and:

<!DOCTYPE plist PUBLIC "-//Aple//DTD PLIST 1.0//EN">

should be:

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

Best Answer

Related Solutions

MacOS – Derive the launchd config plist based on a launch label

MacOS – Submitting job to launchd gives error “no plist returned”, “nothing found to load”

Related Question