![]() So I have to assume the default user 'syncthing' (or the entire 104 container) does not have permission to write to the /r720xd1/subvol-108-disk-0 - presumably because this is the subvol for a different container. When I try to create a new 'test' Folder to share via Synthing from the webGUI I receive:įailed to create folder root directory mkdir /r720xd1/subvol-108-disk-0/syncthing/test: permission denied. I logged in to the Syncthing webGUI from a client on the LAN and changed Actions>Settings>Default Folder Path to: r720xd1/subvol-108-disk-0/syncthing This was done in an attempt to directly access the shares in my TKL File Server directory. Subvol-104 was created when I added a mountpoint /r720xd1/subvol-108-disk-0/syncthing. This was done to utilize the ZFS file system as the storage for TKL File Server shares. Subvol-108 was created when I added a mountpoint of /srv/storage for the TKL File Server. r720xd1/subvol-108-disk-0 # For TKL File Server r720xd1/subvol-104-disk-0 # For TKL Syncthing r720xd1 has two subdirectories for two containers running under PVE: The ZFS pool is mounted to the PVE host as /r720xd1 All shares in TKL File Server are working great - r/w accessible by clients on the LAN. On the r720xd, I have a ZFS pool created, which is currently only used for TKL File Server as a NAS. I have the Syncthing CT installed and running. I wish to see this implemented at some point.I am trying to setup TKL Syncthing on a r720xd server running Proxmox VE 5.4-11. Start is to save on processing therefor gaining extra battery time. Well, that is not a feature is it? I mean opening and closing an appĪnyway the issue with that approach is that it would trigger extra To the usage experience when syncthing would ideally be fire and forget Workaround instead of a real fix and I think it adds unnecessary friction Low? On Android it's meant as a safeguard against automatic changeĭetection not working (Felix correct me if I'm wrong).Īnyway, imo if there is indeed a battery issue, this is a user facing You can see the refresh interval of your folders, maybe they are set too In the Android system actually stops when you press back and stop seeingĪs for the battery concern, I have not seen the drain you are experiencingĪnd I have used the app on several low end devices. I may be understanding your request wrong but if you disable "run inīackground" you are essentially getting what you asked. However I am not seeing this functionality anywhere on the ui. This functionality can not be used together with wifi/charging settings.īy default, this is set so that syncthing is only active when requested, " Added functionality to manually stop sync (fixes #131). it does it only when the suer asks for a fix f383393 That way the binary is paused (or something like that) and check for files modifications etc. ![]() It would be nice to have the synthing app running in the bg but the user should be able to control a stop and start process of the Syncthing binary. Also the Battery app shows that most of the battery was used by the ST app. Sometimes I find my battery drained %30 in less than 10 minutes by the Sycnthing app and I can see that the syncthing.so runs and uses alot of cpu for no apperant reason (even when there should not be any updates from other clients or from a non existing file update). The android app uses alot of cpu for no apperant reason.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |