I don't know if I got your question right, but puppet actually generates a "file metadata" consisting of a unique hash (md5) for a file content. The update only happens when the md5 hash from local differs from the server.
So actually, the puppet client asks for the file_metadata for the source, like GET /production/file_metadata/module/file.conf it returns *only* the md5 hash from the file on the server. Then it generates the hash from the local file. If the local hash is different, the client gets the file from the server GET /production/file_content/module/file.conf And updates on the local system. Is that it? :-) -- []'s Hugo www.devin.com.br 2011/3/29 metalove <[email protected]> > sorry for confusion. > > What I meant was, if > > -. the same file is between puppet daemon(server) and client > -. the timestamp was older at puppet server, > > I think that puppet client should not update, right? > but puppet client seems update even the server's file is old.... > > so, what I should do, not to update the old file from server? > > > puppet client <--------------> puppet server > > index.html index.html > 2011-03-29 2011-03-28 > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
