I means the second (the file's last modification timestamp (mtime) as recorded in its file metadata in the file system).
OK, thanks anyway for the clarification. On Monday, January 5, 2015 9:10:55 AM UTC-5, jcbollinger wrote: > > > > On Friday, January 2, 2015 2:48:00 PM UTC-6, [email protected] wrote: >> >> Hi guys, >> >> I am wondering if there was an option to preserve the original timestamp >> when copying a file? Right now the timestamp is updated every time the file >> is recopied. I don't want that. >> >> I am using open source Puppet 3.7.3. >> >> > > It depends. Are you talking about a timestamp recorded in the file's > content, or are you talking about the file's last modification timestamp > (mtime) as recorded in its file metadata in the file system? > > If the former, then it's a question of how you generate the content > (template and/or concatenated fragments) and of how you evaluate whether it > is in sync. In that case, you haven't provided enough information for us > to make any specific suggestions. > > If the latter, then no, Puppet does not have any built-in mechanism > providing for lying to the OS about the last access or modification time of > files it manages. If this is indeed what you are trying to do then I urge > you to choose a different approach, because anything built on deliberate > (meta)data falsification is going to be troublesome and brittle. > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6eb45b0d-d6c5-4ccc-8fb4-c5355065f687%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
