Hi Zenju,
first of all thanks for the great tool. I am playing around with it for some weeks now trying to get some sync stuff running in my private computer network at home.
One part of what I am trying to do is based on RealTimeSync. However, this seems not to be working correctly in all cases.
Setup: I use RealTimeSync with a ffs_real file on a Windows 10 machine. The icon shows the read arrows, but now comes the point: If I use small delays (I tested 1s and 10s), the sync is started if I change something. However, for larger delays (I tested 50s and 60s, the batch file is never executed, even if a add new files or save an old one.
If I double click on the icon, change the delay from 50 or 60s back to 10, and confirm, the sync starts after 10s... (and the other way round). Any idea why the larger delays do not work?
(Just for information: I was just testing some configuration. In my case, even the scanning lasts several minutes, so the delay might by unimportant, but still I wanted to report...).
Thanks again and best regards
Michael
Edit: Forgot to say: I am using the latest version, i.e. 10.24.0.0
Edit 2: I just noticed that I have included %userprofile%, which includes the AppData directory. In the 10s variant, this leads to the fact that the batch file is every time 10s after the sync ended, while (due to an exclude in the batch file) the AppData dir is not synced (log file: Nothing to sync...). Maybe this is important for the behaviour I noticed above as well?
RealTimeSync not working for larger delays
- Posts: 3
- Joined: 8 Jun 2020
-
- Posts: 4056
- Joined: 11 Jun 2019
Sounds like there is a change within the larger idle times that resets the timer. Appdata will most likely be the cause
- Posts: 3
- Joined: 8 Jun 2020
But a change should trigger sync and not reset the timer, right? For shorter times, the changes do also occur arbitrarily and not at the time point that RTS checks for changes. Also, if a sync is detected, FFS runs for several minutes, and afterwards changes are also detected again correctly if the time interval is small...
BTW: Is there a way to also exclude subfolders from RTS supervision, like AppData? Otherwise sync is started and ends with "Nothing to sync".
BTW: Is there a way to also exclude subfolders from RTS supervision, like AppData? Otherwise sync is started and ends with "Nothing to sync".
-
- Posts: 2450
- Joined: 22 Aug 2012
RTS starts the FFS sync after a specified idle-time (default: 10s), not a delay-time.
Upon detecting a change in the monitored folders, RTS postpones launching FFS until no new/further changes in the monitored folders have occurred for a duration of the idle time.
See here, below Limitations.
So, like xCSxXenon stated, the idle timer is reset upon each detection of a change in the monitored folders.
It is therefore best to keep the scope of the RTS monitored folders limited, and not make it too big/wide.
With a wide scope, the risk that any program creates or modifies a file anywhere in the RTS monitored folders during the idle time increases, particularly when using a large idle time. Thus, RTS may postpone launching FFS indefinitely.
There is no way to exclude (certain) (sub)folders in RTS.
But also in light of the above, it is better to use multiple RTS instances, each monitoring one or more specific folders and their subfolders, and each launching a specific FFS sync with a scope equal to the monitored folder(s) of the RTS instance.
Upon detecting a change in the monitored folders, RTS postpones launching FFS until no new/further changes in the monitored folders have occurred for a duration of the idle time.
See here, below Limitations.
So, like xCSxXenon stated, the idle timer is reset upon each detection of a change in the monitored folders.
It is therefore best to keep the scope of the RTS monitored folders limited, and not make it too big/wide.
With a wide scope, the risk that any program creates or modifies a file anywhere in the RTS monitored folders during the idle time increases, particularly when using a large idle time. Thus, RTS may postpone launching FFS indefinitely.
There is no way to exclude (certain) (sub)folders in RTS.
But also in light of the above, it is better to use multiple RTS instances, each monitoring one or more specific folders and their subfolders, and each launching a specific FFS sync with a scope equal to the monitored folder(s) of the RTS instance.
- Posts: 3
- Joined: 8 Jun 2020
Hi Plerry,
thanks for the explanation. Now I see what happens. But to be honest, your explanation is much clearer than that on the website.
I will try if I can find a good way to realize what you proposed by focusing the scope. My scope is the user's profile folder in Windows (which includes Documents, Pictures, Music and several more depending on which programmes you use that add folders there) EXCEPT the AppData folder (which makes no sense to sync at least during a user being logged in).
Thanks again for your help!
thanks for the explanation. Now I see what happens. But to be honest, your explanation is much clearer than that on the website.
I will try if I can find a good way to realize what you proposed by focusing the scope. My scope is the user's profile folder in Windows (which includes Documents, Pictures, Music and several more depending on which programmes you use that add folders there) EXCEPT the AppData folder (which makes no sense to sync at least during a user being logged in).
Thanks again for your help!
- Posts: 6
- Joined: 6 May 2020
I have a problem with a similar item.
When RTS monitores my download folder it should start syncing when there was no download/copying/moving, etc. for more than 10 seconds (or individual idle time). But it starts every 10 seconds and syncs every new downloaded byte without waiting for a break. That's anoying because it slows down my working processes. Is there any possibility to tell RTS to sync only every 15 Minutes or when no data is written or read in the monitored folders?
When RTS monitores my download folder it should start syncing when there was no download/copying/moving, etc. for more than 10 seconds (or individual idle time). But it starts every 10 seconds and syncs every new downloaded byte without waiting for a break. That's anoying because it slows down my working processes. Is there any possibility to tell RTS to sync only every 15 Minutes or when no data is written or read in the monitored folders?
