I read often about SR having problem detecting changes in some file for whatever reason.
Why not a "force sync" section in the config file that always syncs a directory or type of file(s)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are very, very, very few and convoluted scenarious where a file is changed and snapraid can't detect the change. Except for truecrypt/veracrypt containers where there's a config flag to let truecrypt update the timestamp on the container.
Apart from that you WANT to catch all the times when snapraid stops because such errors, because they are disk or memory issues.
If you DO have files that change often without touching the timestamp anyway you have a bigger problem than snapraid stopping each time it reads AGAIN such file - the problem that it won't DETECT changes in other changed files (the ones it DOESN'T have to read again when doing sync).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I read often about SR having problem detecting changes in some file for whatever reason.
Why not a "force sync" section in the config file that always syncs a directory or type of file(s)?
There are very, very, very few and convoluted scenarious where a file is changed and snapraid can't detect the change. Except for truecrypt/veracrypt containers where there's a config flag to let truecrypt update the timestamp on the container.
Apart from that you WANT to catch all the times when snapraid stops because such errors, because they are disk or memory issues.
If you DO have files that change often without touching the timestamp anyway you have a bigger problem than snapraid stopping each time it reads AGAIN such file - the problem that it won't DETECT changes in other changed files (the ones it DOESN'T have to read again when doing sync).