I''d like to add $HOME/.profile to user accounts using a template. However, I''d like to allow users to edit their profiles after they have access. Is there a way to configure puppet to place $HOME/.profile on the system if it''s not there but NOT SYNC against the puppet master if it is changed? TIA, Jeff --~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Jeff wrote:> I''d like to add $HOME/.profile to user accounts using a template. > However, I''d like to allow users to edit their profiles after they > have access. Is there a way to configure puppet to place > $HOME/.profile on the system if it''s not there but NOT SYNC against > the puppet master if it is changed?In the general case - no. Puppet doesn''t have the idea of "one shot" policies. In this specific case, though, you can use Puppet to manage the files contained in the /etc/skel directory. http://www.linfo.org/etc_skel.html The contents of this directory are copied into new user accounts when they''re created, so this should give the effect that you''re looking for. -- Frank Sweetser fs at wpi.edu | For every problem, there is a solution that WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC --~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hi>> I''d like to add $HOME/.profile to user accounts using a template. >> However, I''d like to allow users to edit their profiles after they >> have access. Is there a way to configure puppet to place >> $HOME/.profile on the system if it''s not there but NOT SYNC against >> the puppet master if it is changed? > > In the general case - no. Puppet doesn''t have the idea of "one shot" policies.hmm for the file case imho yes it have: http://reductivelabs.com/trac/puppet/wiki/TypeReference#file "replace Whether or not to replace a file that is sourced but exists. This is useful for using file sources purely for initialization. Valid values are true (also called yes), false (also called no)."> In this specific case, though, you can use Puppet to manage the files > contained in the /etc/skel directory. > > http://www.linfo.org/etc_skel.html > > The contents of this directory are copied into new user accounts when they''re > created, so this should give the effect that you''re looking for.this also a good way,maybe even the better and less error prone. greets pete --~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
2008/6/19 Frank Sweetser <fs@wpi.edu>:> > In this specific case, though, you can use Puppet to manage the files > contained in the /etc/skel directory. > > http://www.linfo.org/etc_skel.htmlThis is what I do. The downside is that if you update the contents of /etc/skel with a new file, only accounts after that update will get it, existing accounts won''t. --~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Duncan Hill wrote:> 2008/6/19 Frank Sweetser <fs@wpi.edu>: >> In this specific case, though, you can use Puppet to manage the files >> contained in the /etc/skel directory.Mrrhgm. Pushing out files with replace => false is the correct way to achieve this. That way you can manage the permissions on them effectively, and ensure they''re present for every managed user account. Regards, AJ --~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Thu, Jun 19, 2008 at 6:52 AM, Duncan Hill <bajandude@googlemail.com> wrote:> > 2008/6/19 Frank Sweetser <fs@wpi.edu>: >> >> In this specific case, though, you can use Puppet to manage the files >> contained in the /etc/skel directory. >> >> http://www.linfo.org/etc_skel.html > > This is what I do. The downside is that if you update the contents of > /etc/skel with a new file, only accounts after that update will get > it, existing accounts won''t. >My $.02 - (I''m speaking from a linux point of view) Why not manage all of the organization wide settings through /etc/profile? If you have different groups of user that need different settings, use a case statement within /etc/profile. $HOME/.profile (by default) get''s sourced after /etc/profile. If you don''t want a user to have to ability to override a env setting, set it to "readonly" in /etc/profile. That way you can manage the profiles through puppet and still give users the ability to customize their environment. Here''s an example of setting the session timeout (that can''t be overridden) with /etc/profile: # Idle Timeout case "$UID" in 0|20068|20098) TMOUT=; ;; *) TMOUT=900; readonly TMOUT; ;; esac Jeff --~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---