I have a splink class i can share once I get back to the office.  
Creating the user/group first is the best approach.

Ed

Sent from my iPhone

On May 14, 2009, at 11:40 PM, Jeremy Hansen <jer...@skidrow.la> wrote:

>
> If there's a section in the documentation that highlights this, please
> feel free to point me in the right direction.  I am definitely a  
> beginner.
>
> I'm trying to build a recipe to install splunk clients on all our
> hosts.  Splunk is a commercial log aggregation utility.  The RPMs  
> splunk
> distributes breaks a lot of rules in terms of RPM standards.  I'm  
> trying
> to use puppet to alleviate some of this pain and find work around  
> where
> the rpm fails.
>
> The splunk rpm tries to dynamically allocate uid and gid during its
> installation.  This is bad for us because we use ldap and uid/gid may
> not be reflected in local files.  So I figured I could use puppet to
> create the splunk user FIRST to dictate a static uid/gid and then
> install the package, but I can't seem to figure out how to tell puppet
> to install the user first and then install the package from our yum  
> repo.
>
> Then after the package is installed, splunk has some commands to  
> enable
> itself in init.  I'd like that to run AFTER the package install.  Then
> there's a couple other commands to put splunk into the right mode.
>
> How do I dictate the order of how things get executed?  Right now it's
> installing the package first, then doing a usermod/groupmod to set the
> uid/gid and it's trying to run the init commands before the package is
> installed, etc.
>
> Thanks
> -jeremy
>
> >

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to