Wietsche

Hi! I can confirm that this is now resolved. Thank you so much! Cheers! W

Fantastic! Thank you very much!

Thanks @wabun ! Exactly that. Glad it was not just me. I am also very appreciative of this docker container! Thanks for the work! Please have a look if this can be fixed. If one needs automatic syncing, that functionality should be accessed with scheduled jobs. Cheers, W

Hi, Thanks for getting back to me. I will make a screen recording of this and share it as soon as possible. It was doing this from the start. I have one scheduled job, but that was set up later and after the fact. I'll disable it just to make sure. I'll get back to you. With thanks, Wietsche

Hi! The moment you start the docker container, FreeFileSync starts to compare the folders from the last sync session. The destination folder is not available all the time. This causes the drives in unraid to spin up, to access the source folders, and then an error message appears when the destination folders are unreachable. The knock on problem it then causes is that the drives will not spin down again, since it is in use, and you have to log in and cancel the "comparison" before your unraid server will spin down the drives and quiet down. I have FreeFileSync on my Windows PC, and it does not have this behavior. I think there is a setting somewhere that toggles this "compare at startup" behavior. I can't see or find the option in the UI of the docker version. Hope this makes more sense now. Any help to get this disabled will be greatly appreciated. Thanks!

Anyone know how? Please help?

Hi, Is there a way to disable the the automatic "compare", of the previous session, when you start the docker container? I don't want it to do anything unless a scheduled sync batch job is started. I could not find such an option in the menus. Cheers!

Hi. Anyone having issues with this plugin with a Corsair Commander Pro installed, with interface for the plugin stop listing any sensors and breaking the dashboard temperature and fan values, please see the solution here: https://github.com/lm-sensors/lm-sensors/issues/369 I can confirm it works with the wildcard option. Files to be changed for a permanent config fix (persisting after a reboot): >> /etc/sensors.d/sensors.conf >> /boot/config/plugins/dynamix.system.temp/sensors.conf You can check if the files above are correct if you run "sensors" in the terminal and it responds with all your sensor values. Hope this helps someone. Cheers, W