Bcfg2 should not update mtime on metadata changes

[https://www.google.com/accounts/o8/id?id=AItOawlgX-1giylmugdMyws_Brrk63uA_dyfDnU]

When permissions or ownership of a file change, Bcfg2 is not only updating the file metadata, but also the file itself. So an update to the user, for instance, will also cause the entire file to be rewritten. This affects both mtime and ctime.

Note, however, that subsequent Bcfg2 calls will still chmod/chown the file and update the ctime, even though the permissions are the same--but will not actually modify the file.

This is a problem for programs that use mtime to determine whether or not to refresh changes from the disk, and can produce unexpected results.

[solj]

Replying to https://www.google.com/accounts/o8/id?id=AItOawlgX-1giylmugdMyws_Brrk63uA_dyfDnU:

When permissions or ownership of a file change, Bcfg2 is not only updating the file metadata, but also the file itself. So an update to the user, for instance, will also cause the entire file to be rewritten. This affects both mtime and ctime.

I think we should be able to fix this by creating file hashes on the server and comparing them to the file contents of the client.

Note, however, that subsequent Bcfg2 calls will still chmod/chown the file and update the ctime, even though the permissions are the same--but will not actually modify the file.

The Installfile method in browser:src/lib/Client/Tools/POSIX.py should only be called when the file is incorrect. I don't see where this could be happening.

[solj]

This seems a bit invasive for a bugfix release. Moving to 1.3.