In my case the developer may not have root access On Jan 19, 12:39 pm, Trevor Vaughan <tvaug...@onyxpoint.com> wrote: > As this would generally be a manual change, I would use 'chattr +i' on > Linux systems. > > Trevor > > > > > > On Tue, Jan 19, 2010 at 3:14 PM, jb <jeffb...@gmail.com> wrote: > > I'd like others to have the option to temporarily disable puppet from > > modify a file or directory...something along the lines of: > > > ./something.conf.lock > > > causes > > > ./something.conf > > > to NOT be modified by puppet for as long the lock file exists > > > it'd also be nice to be able to disable an entire directory from being > > modified if the file: > > > ./PUPPET-DISABLE > > > is present. basically the 'unless' parameter as is present in the Exec > > type... > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group. > > To post to this group, send email to puppet-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/puppet-users?hl=en. > > -- > Trevor Vaughan > Vice President, Onyx Point, Inc > (410) 541-6699 > tvaug...@onyxpoint.com > > -- This account not approved for unencrypted proprietary information --
-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
