Well, I ended up writing a script that pulls the information from the
localconfig.yaml file and then stole bits from ralsh to see what
services were on the system and turned off everything that shouldn't
be active.
And yes, I do want to specify all services that should be running on the system.
Interestingly, the following definition says that the service should
exist, but to let it be whatever it is:
service { "foo": }
On this same note, how would I go about using the Puppet service
provider in ruby code to turn off unwanted services? I just hand
jammed it for now, but it would be nice to use the abstraction that is
so nicely provided.
Thanks,
Trevor
On Mon, Nov 2, 2009 at 15:49, Digant C Kasundra <dig...@stanford.edu> wrote:
>
>
> ----- "Trevor Vaughan" <peiriann...@gmail.com> wrote:
>
>> All,
>>
>> I'm looking for a way to obtain information about the managed
>> services
>> on a given client system.
>>
>> Basically, some way to know what services have been enabled by Puppet
>> from the client.
>>
>> I'm hoping to implement something like 'purge' for services such that
>> any service that is not defined is disabled and turned off.
>>
>> Any ideas on how to do this would be welcome.
>
> If you want to know what services Puppet has managed on a client, you can
> look at the yaml file, or you can use store configs and poke at the DB. The
> problem with purging services is do you really want to define everything you
> know to expect on a server in Puppet?
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
