Problem with ftp sync

Posts: 6 · minogig 28 Mar 2024, 07:48

Good morning.
I created a service that synchronizes the files present on a drive folder with a folder present on a hosting via ftp.
In detail the synchronization is mirror-like.
The source folder is the one on the drive, while the destination folder is the one on the server.
As long as I activate the service manually everything works great, when I create real-time synchronization it gives me this error "ftp protocol does not support directory monitoring".
How can I solve this problem?

Posts: 3603 · xCSxXenon 28 Mar 2024, 14:10

Remove the FTP location from being monitored in RTS

Posts: 2283 · Plerry 29 Mar 2024, 11:02

> How can I solve this problem?

That depends on what you consider to be the problem.
• If you consider the error message to be the problem, act as per xCSxXenon's reply.
• If you consider the ftp protocol not supporting directory monitoring to be the problem, you can either use a different protocol (than ftp), one that does support directory monitoring, or you have to learn to live with it. FFS can not solve this for you.

Posts: 6 · minogig 1 Apr 2024, 15:47

Remove the FTP location from being monitored in RTS xCSxXenon, 28 Mar 2024, 14:10

Thank you for your answer. I tried your solution, but as soon as I click on start it tells me this time that it cannot monitor the folder on the drive

Posts: 3603 · xCSxXenon 1 Apr 2024, 17:01

Post a screenshot of the RTS configuration window

Posts: 6 · minogig 2 Apr 2024, 06:53

Post a screenshot of the RTS configuration window xCSxXenon, 01 Apr 2024, 17:01

Thanks for your time

Posts: 2283 · Plerry 2 Apr 2024, 11:59

So, you did not remove the FTP connected location (your top location) in the list of folders to be monitored by RTS.
Click the minus-icon in front of your FTP location.

Posts: 6 · minogig 2 Apr 2024, 13:49

So, you did not remove the FTP connected location (your top location) in the list of folders to be monitored by RTS.
Click the minus-icon in front of your FTP location. Plerry, 02 Apr 2024, 11:59

I attach the video where it shows the error

https://screenrec.com/share/56pVkUul3N

Posts: 943 · therube 2 Apr 2024, 14:46

(Your email is in the video, if that matters to you.)

Shouldn't ? the RTS be running a BatchDriveFtp.ffs_real rather then _batch?

Posts: 6 · minogig 2 Apr 2024, 15:32

(Your email is in the video, if that matters to you.)

Shouldn't ? the RTS be running a BatchDriveFtp.ffs_real rather then _batch? therube, 02 Apr 2024, 14:46

Thanks for the advice. I deleted the video. Then if you need it I'll make another one.
As for your final question it is using batch

Posts: 3603 · xCSxXenon 2 Apr 2024, 16:03

Google Drive also cannot be monitored. You cannot use RTS for this

Posts: 2283 · Plerry 2 Apr 2024, 17:29

> Shouldn't ? the RTS be running a BatchDriveFtp.ffs_real rather then _batch?

No, upon detecting any changes in the monitored folder(s) (if supported), RTS launches its command line, and here should launch FFS to run the sync configuration saved in the specified *.ffs_batch file.

An *.ffs_real file is a file that stores a specific RTS configuration, and contains the folder(s) to be monitored, the Idle Time and the command to be executed upon detecting changes in the monitored folder(s).
The *.ffs_real file is to be specified when invoking RTS, as described here, not when launching FFS (e.g. from the RTS command line).