Hi,
I was testing FreeFileSync and seems everything I need. But I can't get it to work with SFTP.
What I tested
- In FreeFileSync create a 2 way sync with SFTP (authentic: ssh agent)
- do a sync, successfully
- save as batch job
- Open RealTimeSync
- Drag n drop the batchfile & start
- Make changes. Wait a minute, nothing.
So to test I do the same process but with 2 local folders, no SFTP. Then RealTime sync will work, and save logs in .config/FreeFileSync/Logs
I'm on Ubuntu 19.10 fully updated
Am I doing anything wrong? Is their some additional information I should provide?
Thanks
RealTimeSync does not work with SFTP on Ubuntu
- Posts: 2
- Joined: 26 Jan 2020
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
viewtopic.php?t=4418
but local changes should still be detected and trigger a sync.
but local changes should still be detected and trigger a sync.
- Posts: 2
- Joined: 26 Jan 2020
Hi Zenju,
I tried both ways but no it doesn't.
And if both ways don't work it's not very usefull.
I'll go play around with the cron.
Thanks for the reply.
I tried both ways but no it doesn't.
And if both ways don't work it's not very usefull.
I'll go play around with the cron.
Thanks for the reply.
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
"both ways"? You should get an error "The SFTP protocol does not support directory monitoring", then if you remove the folder in RTS, local changes should be detected and trigger the command line (doesn't matter if this is a FFS two-way sync or not).
- Posts: 8
- Joined: 18 Mar 2020
If this is a cron problem then, as well as the variable "DISPLAY=:0" you usually need "XAUTHORITY=/home/<your user name>/.Xauthority". I used to use the GNOME cron GUI tool but it is no longer supported on my SUSE 15.1.( I am trying to fix this). This tool actually did it's work using Python scripts so it was already running on your desktop whereas CRON knows nothing about your desktop. This is why the two variables are required. There is a KDE tool called "task scheduler". Although not as nice as the GNOME tool is does let you set the CRON variables separately. This makes the CRON command easier to build.