Re: Best practice for users/groups on solaris

seph
Fri, 09 Nov 2007 16:32:01 -0000

And to follow up to myself...

I can''t quite make the virtual resources work the way I want them
to. I''d rather not have inapplicable user groups created, which
implies I should use virtual groups. But, virtual groups don''t get
realized when the user is realized. Which leads me separately
realizing the groups, which is a lot of overhead. So I feel like I''m
doing this wrong, and fighting the system.

seph

seph <seph@directionless.org> writes:

> Mike Renfro <renfro@tntech.edu> writes:
>
>> On 11/8/2007 4:18 PM, seph wrote:
>>
>>> The virt_all_users way of managing users seems pretty reasonable,
but
>>> I don''t see how to deal with user specific groups with
that.
>>>
>>> But realizing that on a solaris machine generates an error because
>>> group 1001 doesn''t yet exist. Specifically:
>> I''d guess that you need to define some groups ahead of time:
>>
>> @user { "seph":
>>      ensure  => "present",
>>      uid     => "1001",
>>      gid     => "seph",
>>      comment => "seph",
>>      home    => "/home/seph",
>>      shell   => "/bin/bash",
>>      require => group["seph"]
>> }
>>
>> group { "seph":
>>      ensure  => "present",
>>      gid     => "1001",
>> }
>
> Yes, but I''m not quite sure what the accepted best practice for
this
> is. I''m inclined to drop virt_all_users, and move to having each
user
> and group entries in manifests/users/username.pp, but I''m
wondering
> how other people lay it out.
>
> seph
> _______________________________________________
> Puppet-users mailing list
> Puppet-users@madstop.com
> https://mail.madstop.com/mailman/listinfo/puppet-users