Issue #15719 has been updated by James Turnbull. Category set to provider Status changed from Unreviewed to Accepted
I can validate this. Looking at the k5login type it needs a refacter. ---------------------------------------- Bug #15719: k5login does not track setuid mode https://projects.puppetlabs.com/issues/15719#change-68831 Author: Ken Dreyer Status: Accepted Priority: Normal Assignee: Category: provider Target version: Affected Puppet version: Keywords: Branch: The Puppet Style Guide says "File modes should be represented as 4 digits rather than 3, to explicitly show that they are octal values." This exposes a small bug in the k5login type. A sample k5login.pp manifest: k5login { '/root/.k5login': ensure => present, mode => '0400', } Puppet applies the setuid "change" on each run: # puppet apply k5login.pp notice: /Stage[main]//K5login[/root/.k5login]/mode: mode changed '400' to '0400' notice: Finished catalog run in 0.03 seconds # puppet apply k5login.pp notice: /Stage[main]//K5login[/root/.k5login]/mode: mode changed '400' to '0400' notice: Finished catalog run in 0.03 seconds Like the current File type, the K5login type needs to be "setuid aware". -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
