Issue #6004 has been updated by Daniel Pittman.

Jo Rhett wrote:
> Markus Roberts wrote:
> > Thanks for the additional information on this (grumble) ongoing issue.
> 
> Can you please reference the bug this duplicates, so we know where the patch 
> will be?

Unfortunately, no.  I have no idea what Markus was thinking of way back when, 
and unless he steps up - since he no longer works with us - I don't think we 
have any way to recover that detail.
----------------------------------------
Bug #6004: checksum => mtime still reads the source and target files
https://projects.puppetlabs.com/issues/6004

Author: Daniel Piddock
Status: Duplicate
Priority: Normal
Assignee: 
Category: file
Target version: 
Affected Puppet version: 2.6.4
Keywords: 
Branch: 


Copying a file with checksum set to mtime still causes both the target and 
source file to be read (and md5summed?)

    file { '/tmp/foobar2':
        source   => '/tmp/foobar1',
        checksum => mtime,
    }

strace of puppet shows that the source and target files are still being read 
even when the timestamps of the files haven't changed.

If the target is missing:

* open,read,close source
* test for target, not present
* open target.temp
* open,read,close source
* write,close target.temp
* open,read,close target.temp
* rename target.tempt to target
* open,read,close source

If the target was present:

* open,read,close source
* open,read,close target

Attached straces. Source is /tmp/foobar1, target is /tmp/foobar2, content is 
"foobar1content"


-- 
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.

Reply via email to