Based on 000xx.log file in index-v0.11.0.db is written very frequently, it seems that hard drives cannot go to sleep as long as there are paired clients online because there is continuously data written to the local database like “last seen” time etc.
This basically defeats my idea of using Syncthing to replicate my music library from the HDD-backed NAS to a SSD-backed Raspberry for power saving reasons.
Is there a way to configure that, like e.g. that such volatile data is held in RAM instead of in the DB or that “last seen time” is not tracked for a specific client?
1 post - 1 participant