Looking for best practice to call ffs_batch files

[valbo]

Hi everyone,

I have a question on how to best use FFS in regards to what "comes before" it is triggered.
What I mean is the following : I would like to use FFS from a command, using the generated .ffs_batch file.
But for that, I would like to monitor a folder (or a specific file), and following some rules (for example every 5 changes, or every hour, whatever comes first), to call the .ffs_batch file to proceed with the sync.
So that everything is sort of programmatic and wont need my interaction.

I am wondering if any of you is doing such, and if so, if you can share which tool are you using ?

I found two softwares to monitor folders : FolderMonitor and FileWatcherUtilities, both of them are good for monitoring and have options to call a script with arguments.
Then I have a .bat file that proceeds with doing the checks i want (5changes, 1hour buffer), and call the .ffs_batch file.
My current issue, is that if I have for example 5 files changes, then the softwares to monitor the folders will call my .bat file 5 times, and with the creation of the *.ffs_lock, *.ffs_tmp, *.ffs_db files, it goes into an endless loop and get messy...

So, I figured that I am not the only one to potentially have the same need, and wondered how are you using FFS triggers (what calls the FFS .ffs_batch files)..

thanks for any help !

[xCSxXenon]

Use RealTimeSync, bundled with FFS already. Use Task Scheduler for periodic syncing in Windows.

[therube]

(If you do go your original route, you might also check out, https://www.nirsoft.net/utils/folder_changes_view.html.)

[valbo]

thanks for your answers

@therube : i am a big fan or Nirsoft, but in that case, it wont work : i can't find how to exclude "*.ffs_lock, *.ffs_tmp, *.ffs_db" files, so it goes into an endless loop.
@xCSxXenon : RealTimeSync could be the solution, i need to test it out a bit further but didnt notice that piece of useful addon...because it's not "instant" the .ffs_batch script isnt triggered multiple times, and it skips the other ffs_ files. i think that should solve it, thank you :)

[Plerry]

You won't end up in an endless loop, because (a per the RTS Manual page):

While RealTimeSync is executing the command line, monitoring for changed files is temporarily inactive.

[xCSxXenon]

You won't end up in an endless loop, because (a per the RTS Manual page):

While RealTimeSync is executing the command line, monitoring for changed files is temporarily inactive.

You missed where that was referring to usage of the Nirsoft utility.

[Plerry]

I did not miss that, but simply explained why, when using RealTimeSync (as opposed to e.g. Nirsoft), you don't run the risk of ending up in an endless loop.