Fire-and-forget process

[gaak]

Hi,
I need to set something similar to the following example:

I have one sync batch job with two folder pairs: t1 - t2 and t2 - t3.
Folder t1 contain t1.txt file,
t2 contains t2.txt and
t3 contains t3.txt file
Is it possible to set the following in this ONE sync batch job
(Synchronization setting is UPDATE) :
1. synchronize folder pair t1-t2 (after it is done, t2 should contain both t1.txt and t2.txt file)
2. synchronize folder pair t2-t3 (after it is done, t3 should contain both t1.txt and t2.txt file and t3.txt)

It looks to me that before the synchronization is started, the program takes
current folder structure and content included in folder pairs, and NOT before
every folder pair synchronization.
It looks like Fire-and-forget process.
Here is log that confirm my doubt.

10/03/12 - SyncJob: Synchronization completed successfully!

Items processed: 2 (14 Bytes)
Total time: 00:00:00
___________________________________________________________

Info: Start comparison
Warning: A folder will be modified which is part of multiple folder pairs.
Please review synchronization settings.
'D:\test\t2\'
Info: Synchronizing folder pair:
Left: 'D:\test\t1\'
Right: 'D:\test\t2\'
Info: Creating file 'D:\test\t2\t1.txt'
Info: Synchronizing folder pair:
Left: 'D:\test\t2\'
Right: 'D:\test\t3\'
Info: Creating file 'D:\test\t3\t2.txt'
Info: Synchronization completed successfully!

Regards!

[Zenju]

No, this is not possible with a single configuration, this is basically what
the warning is trying to say.

[gaak]

And would it be possible to make a script with two sync batch job? How the
script will know if the first sync batch job is completely over in order to
trigger the execution of the second one.

Thanx!

[Zenju]

Sure, that's simple. Just create and start a .cmd file with content similar
to:



"C:\Program Files\FreeFileSync\FreeFileSync.exe" "H:\some folder\SyncJob1.ffs_batch"
"C:\Program Files\FreeFileSync\FreeFileSync.exe" "H:\some folder\SyncJob2.ffs_batch"




> How the script will know if the first sync batch job is completely


FFS has built-in locking that is active by default and makes sure that
different sync jobs don't interfere. In your case it's not even needed, since
you would start both sync jobs synchronously one after the other in the .cmd.
file.

[gaak]

:-)))
Thanks!