On Thursday, May 7, 2015 at 12:32:59 AM UTC-5, Josh Cooper wrote: > > > > On Wed, May 6, 2015 at 7:29 AM, Johnson Earls <[email protected] > <javascript:>> wrote: > >> never mind. puppet agent ignores the user/group config settings, so >> those should be kept at puppet, and ${::settings::user} / >> ${::settings::group} should not be used to configure agent-related options >> (such as file ownership). >> > > The `puppet` user and group are really server-side settings, to specify a > less privileged account to run the webrick/passenger/puppetserver process > as. > >
Right. > To confuse things, `puppet` packages (rpm/deb) have always created the > `puppet` user and group, but was unnecessary on the agent. In Puppet 4, we > have fixed this, so the puppet-agent package does not create a `puppet` > user or group. Only the puppetserver package does that. > So the new package naming confuses even PL itself? I mean, in our recent discussion of the new package naming and versioning <https://groups.google.com/forum/#!topic/puppet-users/K7-tUQoJ9FA>, Eric and Michael asserted that the "puppet-agent" package is the basic Puppet infrastructure package, with which one can run the agent, the traditional rack-based master, and everything else from Puppet's Ruby stack. They claim the "puppetserver" package is *optional*. I completely believe that's the *intention*, but in that case the "puppet-agent" package should be the one responsible for the "puppet" user and group. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6127f5ca-a620-4e92-ab11-9fd8ea41c7d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
