You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Not sure it's a bug or a feature request.
I need to synch 2 folders on a nfs and local drive. The security restrictions are important on the nfs, so I don't have the ability to change the access time on the root directory I want to sync. This triggers the following error :
rsync: failed to set times on "/network/lustre/blah/DATAfolder/.": Operation not permitted (1)
My two questions are:
Is there any way I can turn off setting times on the target directory? or ideally just the root of the target directory?
Is there a chance that this time setting operation of the root directory is actually the last one performed by rsync, or triggers an exception that doesn't halt the execution, so I actually don't care too much...
To Reproduce
Run osync in an environment where times cannot be set on the root target directory.
Environment (please complete the following information):
Full osync version (including build): 2021062901
OS: Linux Mint 19.1 Cinnamon
Bitness x64
Shell (busybox or else) bash
The text was updated successfully, but these errors were encountered:
Sorry for the late reply.
Could you try to add --no-times to RSYNC_OPT_ARGS in config file ?
Be aware that synchroniation is time based, so ignoring access time is okay, mtime isn't.
Describe the bug
Not sure it's a bug or a feature request.
I need to synch 2 folders on a nfs and local drive. The security restrictions are important on the nfs, so I don't have the ability to change the access time on the root directory I want to sync. This triggers the following error :
rsync: failed to set times on "/network/lustre/blah/DATAfolder/.": Operation not permitted (1)
My two questions are:
To Reproduce
Run osync in an environment where times cannot be set on the root target directory.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: