I believe the disabled state is stored in /var/db/launchd.db/ com.apple.launchd/overrides.plist
so to bound ntp, for example: launchctl unload "/System/Library/LaunchDaemons/org.ntp.ntpd.plist" 2> /dev/null /usr/libexec/PlistBuddy -c "set :org.ntp.ntpd:Disabled false" /var/db/ launchd.db/com.apple.launchd/overrides.plist launchctl load "/System/Library/LaunchDaemons/org.ntp.ntpd.plist" 2> / dev/null --- Thanks, Allan Marcus 505-667-5666 On Aug 31, 2009, at 5:55 PM, Nigel Kersten wrote: > > On Sun, Aug 30, 2009 at 6:30 AM, > grandpa<[email protected]> wrote: >> >> Forgot to add that I'm running Snow Leopard... > > I've just had a metric crapload of work get dumped on me today, so if > anyone else feels like having a look at this issue for Snow Leopard, > that would be awesome. > > Essentially we have two main choices: > > a) provide a completely different provider by using the new > ServiceManagement framework that is accessible from Ruby in Snow > Leopard. I've yet to look at this seriously in Ruby, but it is a far > better option than shelling out to launchctl all the time. > > b) provide a slightly different code path by examining the new > locations for launchd job state in Snow Leopard (somewhere in /var) > > Basically the methods that will need to be fixed are: > > status > enabled? > enable > disable > > I think. > > > Option a) is where we eventually want to be. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
