Realsync problem
- Posts: 6
- Joined: 10 Dec 2018
When usinf realsync, once the source folder change the realsync will work, but it will scan all the files and then copy the new file even just for one single file.but the scanning will cost a lot of times to continue. So could it just monitor and copy new file without scanning? thus should be the real meaning of realsyc.
-
- Posts: 2451
- Joined: 22 Aug 2012
RealTimeSync (RTS) will not trigger a FreeFileSync (FFS) sync as soon as a file in the monitored folder(s) has changed. Launching FFS will be "armed" upon detecting such change, but only "triggered" upon detecting that no (further) such changes have occurred for a time specified in RTS (i.e. inactivity regarding write actions in the monitored folder(s) for the RTS specified time)
This prevents too frequent invocation of FFS in case of continuous or very frequent file changes in the monitored folder(s). Hence, upon invocation of FFS multiple files may have changed in the monitored folder(s) and FFS (nor RTS) knows exactly which file(s) have changed. Only by running a compare (your: scanning), FFS will learn the full extent of all changes and consequent actions.
This prevents too frequent invocation of FFS in case of continuous or very frequent file changes in the monitored folder(s). Hence, upon invocation of FFS multiple files may have changed in the monitored folder(s) and FFS (nor RTS) knows exactly which file(s) have changed. Only by running a compare (your: scanning), FFS will learn the full extent of all changes and consequent actions.
