Sorry for multiple threads at once! I have a couple of ideas which could make the app more useful to a lot of people
1. When using an HDD (not an SSD), accessing the filesystem tables is relatively fast, but reading multiple files at the same time gets slow pretty quick. As a result I have to change the thread count to 8 for comparing, but then bump it down to 2 for the actual sync. It would be much easier if there were two columns to set the thread count for each of the stages.
2. Timeout duration change: sometimes the server I'm syncing to freezes the FTP connection during comparison, and it takes about 30-60 seconds for FFS to time out and retry. It would be nice if there was an option to bump that down to 5-10 seconds.
3. I have a physical PC Speaker wired into the PC running FFS in a mostly headless configuration. Then FFS runs a powershell script to play a melody through the PC speaker so that I know the backup succeeded even if I'm not in an RDP connection. However if there is an error, I don't hear anything until I just go to check on it over RDP. If there was an option to run a script on an error event, or just use the Console.Beep for the sounds, that would make it much easier for such setups
Feature requests: threading settings and actions on error
- Posts: 2
- Joined: 16 May 2025
-
- Posts: 2947
- Joined: 22 Aug 2012
3. In the sync settings (F8) you have the option to "Run a command" respectively "on completion", "On errors" and on "Succes". I believe you can only use one of those three (but never tried to use more than one).
However, as described in the FFS manual page on Command Line, you should be able to check the FFS exit code, and play a sound accordingly.
However, as described in the FFS manual page on Command Line, you should be able to check the FFS exit code, and play a sound accordingly.
