thanks for the comments guys
For troubleshooting, what if you change the on-completion command to wait ~30 seconds before the exit command? Then you can watch the sync finish and check the log folder. If the log file doesn't show up until those 30 seconds pass, then you'll know if the log is created before or after the command
xCSxXenon, 13 Jun 2022, 20:46
so, adding a longer wait made it apparent that it's not actually waiting at all
TIMEOUT 30 /NOBREAK & FOR /F "delims=" %f IN ('DIR "%AppData%\FreeFileSync\Logs\*.log" /B /O:-D /S') DO COPY /V /Y "%f" "C:\Users\me\Desktop" & EXIT
this works fine in cmd (waits, then copies, then exits), but as an FFS_batch on-completion command it doesn't actually wait the specified amount of time
would you mind elaborating on this? which feature are you referring to I'm not too familiar with that. wouldn't overriding the log path just create one log at the custom location, not multiple copies of the same log? or am i mistaken about this?
I'm wondering if there is potential for design improvement here, or if your scenario is just special.
Zenju, 18 Jun 2022, 19:07
if i were to guess i would say my use case is probably the odd one out. at the basics, I'm looking for multiple copies of the same log file to be made in different locations. is this something with a sufficiently generalized use? of course it would be great for me if ffs added support for that natively :p