On Tue, Sep 1, 2009 at 3:14 PM, Allan Marcus<[email protected]> wrote: > > I'm going to take my puppet-dev server (running Mac OS X server 10.5.7 > and puppet 0.24.8 and upgrade it to 10.6. I will then install your > puppet and give it a try with some 24.8 clients. Then I'll try it with > some clients using your package.
Brilliant Allan. Much appreciated. > > --- > Thanks, > > Allan Marcus > 505-667-5666 > > > > On Sep 1, 2009, at 3:30 PM, Nigel Kersten wrote: > >> >> so this turned out to not be as much work as I thought it could be, as >> the interaction between the disabled flag in a launchd job plist and >> the overrides plist is much simpler than I thought it was, and I >> decided to only support system level launchd jobs. >> >> At some point in the future I'd like to support user launchds (ie not >> root), but that's going to take a fair bit of design work first. >> >> >> >> On Tue, Sep 1, 2009 at 2:29 PM, Nigel Kersten<[email protected]> >> wrote: >>> yep, see: >>> >>> http://groups.google.com/group/puppet-dev/browse_thread/thread/1ff894c6af240244 >>> >>> for a pending patch. >>> >>> If you could test this, that would be awesome. >>> >>> It's currently at my git repo: >>> >>> http://github.com/nigelkersten/puppet/tree/tickets/0.25.x/2581 >>> >>> >>> >>> >>> On Tue, Sep 1, 2009 at 11:49 AM, Allan Marcus<[email protected]> wrote: >>>> >>>> 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. >>>>> >>>>>> >>>> >>>> >>>>>> >>>> >>> >>> >>> >>> -- >>> Nigel Kersten >>> [email protected] >>> System Administrator >>> Google, Inc. >>> >> >> >> >> -- >> Nigel Kersten >> [email protected] >> System Administrator >> Google, Inc. >> >> > > > > > > -- Nigel Kersten [email protected] System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
