Take the 2-minute tour ×

I have some launchd plists that are now placed at the administrator per-user level, particularly inside:

  • /Library/LaunchAgents
  • /Library/LaunchDaemons

I'd like to avoid that some of those services could start only for one user (possibly avoiding to move all the plists to each ~/Library/LaunchAgents), which is the simplest way?

Edit: To restate, if I have an agent in /Library/LaunchAgent, is there a way to disable it for a particular user or group of users, without copying the plist into each ~/Library/LaunchAgent?

share|improve this question
i'm assuming this is Mac OS X we're talking about? –  quack quixote Apr 22 '10 at 1:46
You'd like to avoid what? –  Hasaan Chop Apr 22 '10 at 7:28
If I have an agent in /Library/LaunchAgent ... is there a way to disable it for an user or a group of users? Without copy the plist in each ~/Library/LaunchAgent... –  user34877 Apr 22 '10 at 9:58
@compriots: that's much clearer, thanks. i've added it into the question body. –  quack quixote Apr 22 '10 at 10:13
@quack...thanks! –  user34877 Apr 22 '10 at 13:08
show 1 more comment

1 Answer

That user would have to explicitly unload the system level job to try to put the cart before the horse.

There is no process to delay a system job until a user logs in so you would have to somehow add that into the launchd code as an extension. It is open source, but it seems like a big undertaking and breaks with the flow of the tool.

share|improve this answer
add comment

Your Answer

