My company is using a build of Ganglia that doesn't handle the user/group creation that is done with the EPEL packages and we were running as nobody. Now I could re-roll my package to do the user creation, which I  should probably do, but this at least ensures that the Ganglia group/user do exist on the system if the package doesn't handle it. The change I made could be improved so that someone could set a different user to run under.



On Nov 11, 2013, at 5:00 PM, Joshua Hoblitt <notifications@github.com> wrote:

> In manifests/params.pp:
> 
> >    # paths are the same for el5.x & el6.x
> >    $web_package_name     = 'ganglia-web'
> >    $web_php_config       = '/etc/ganglia/conf.php'
> >    $web_php_erb          = 'ganglia/conf.php.el6.erb'
> >  
> > +  group { 'ganglia':
> > +    ensure => 'present',
> > +    system => true,
> > +  }
> > +  user { 'ganglia':
> > +    ensure  => 'present',
> > +    comment => 'Ganglia Monitoring System',
> > +    gid     => 'ganglia',
> > +    shell   => '/sbin/nologin',
> > +    system  => true,
> > +    require => Group['ganglia'],
> > +  }
> We might need a 'common' class for resources like these. Why are they needed?
> 
> —
> Reply to this email directly or view it on GitHub.
>