Versioning Linux - Use mtime and not ctime

Get help for specific problems
Posts: 1
Joined: 17 Aug 2006

motiv8d1

I have just started looking at freefilesync on linux (ubuntu) and it looks fantastic, kudos!
Very excited about the versioning, I thought to try it, however, when it timestamps the file (in linux, not sure about windows) it does so with ctime (change time of inode) rather than mtime (last modified time).
This is presenting a problem for me, for example I have made copies of several backup sets from windows files and wanted to use ffs on linux to make a single backup set with file-modifieddatetime.ext for all but the most recent file.
As linux updates ctime (originally used by windows as creation time) when the file is copied across, ffs uses this latest inode change date for its versioning name. I really need it to reflect the mtime and not the ctime.
I think the ideal way to solve this for ffs is to allow a custom mask option in the version naming and relevant variables eg: %file%-%mtime%.ext in linux.
This solution would obviously allow the coverage of a much wider audience than just my issue.
Otherwise are there any ways to do what I want in the renaming using ffs on linux?

Additionally I would appreciate an option (check box maybe) for the versioning rename to "rename newest file" or "rename oldest file", or perhaps someone may have the requirement for "rename all different files with version time".
I am able to gain this effect by a unintuitive use of copy direction and revision folder, however, a explicit options as above would make it much easier and less likely to result in accidental user errors I think.

Thanks again

Jesse
User avatar
Site Admin
Posts: 7282
Joined: 9 Dec 2007

Zenju

The time stamp used for versioning is always "now". This makes sense when one wants to get back in time and find out what file was used at a particular time. (consider the user undoing a change and using a file with an older modification time!). Not sure if there is a better handling than the current one.