Issue #2521 has been updated by James Turnbull.
Category set to file
Status changed from Unreviewed to Needs design decision
Assigned to set to Luke Kanies
Luke - I agree this is an issue? Your thoughts?
----------------------------------------
Bug #2521: file{} should update all timestamps when renaming files from temp
file.
http://projects.reductivelabs.com/issues/2521
Author: volcane volcane
Status: Needs design decision
Priority: Normal
Assigned to: Luke Kanies
Category: file
Target version:
Complexity: Unknown
Affected version: 0.24.8
Keywords:
At present puppet writes new files made with the file resource type using a
temp file then renames the temp file. Ruby rename only updates change time not
mtime.
This is a problem when interacting with daemons that monitor directories for
new files, like /etc/cron.d:
1) puppet creates /etc/cron.d/foo.zxxx
2) crond checks for new files matching its rules, the temp file does not match
does not get noticed, crond saves last checked timestamp
3) puppet renames /etc/cron.d/foo.zxxx -> /etc/cron.d/foo and only ctime gets
updated not mtime
4) crond checks for new files since last check, finds none.
I think puppet should probably touch both mtime and ctime after renaming a file.
--
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://reductivelabs.com/redmine/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
-~----------~----~----~----~------~----~------~--~---
