Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Know which .plist's are disabled #22

Open
hector opened this issue Sep 27, 2012 · 0 comments
Open

Know which .plist's are disabled #22

hector opened this issue Sep 27, 2012 · 0 comments

Comments

@hector
Copy link

hector commented Sep 27, 2012

When you "lunchy start -w myservice" or "lunchy stop -w myservice" the state is saved for next boots. In the past days launchctel was adding a key to the .plist file with the value "Disabled", but since SnowLeopard the .plist file is not changed and it is store elsewhere.

As far as I know, launchctl does not offer a way to know if a .plist file is disabled or not for next boots and having to reboot is tedious... It would be great to have some way to see which .plists are disabled or not.

The "lunchy status" command seems the more appropiated place to me for showing it but since it uses the "launchctl list" output, it would be fair enough something like "lunchy disabled".

A link to an article that explains the new locations where the disabled keys are stored:
http://www.mactech.com/articles/mactech/Vol.25/25.10/2510MacEnterprise-SnowLeopard-launchdandLunch/index.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant