zatricky

Due to the fact that btsync is not yet available pre-packaged for CentOS7, I'm loathe to install it as-is on a particular installation. The server I wish to install it on is a file server that also happens to have KVM virtual guests - thus a workaround is to install it on an Ubuntu Guest which then accesses the file server over CIFS. The main problem in my mind is that I don't think CIFS supports inotify properly - but that shouldn't be an issue because nothing other than btsync will be accessing the storage directly. Are there any other pitfalls to doing it this way or other alternatives? Also, anybody had experience doing this the same or similar way? Worst-case I'll just install btsync directly on the CentOS7 server anyway. It just feels messy to be installing things without using the package manager.

Option to treat a peer as a "preferred metadata intermediary" or to automatically negotiate this in some way. Though it isn't a crazy amount of total data, as you add each device to the network, the "idle" network chatter increases dramatically, causing a concern for Internet users with slow (dialup, diginet, shared), shaped, and/or capped accounts. For example, two locations: Location a: A number of desktops/servers connected to each other via decent Local network but connected to the Internet via an uncapped-but-heavily-shaped 384k Internet service Location b: As above but with high-speed unshaped Internet service (40Mb-plus) Location a devices would swarm with each other and, except for one of them, could be configured to not automatically connect to the peers in location b when transferring metadata except if their "preferred intermediary" indicates there is an issue connecting to the peers in location b. Location b devices would swarm with each other and behave the same as with location a. I can imagine two ways to do this, in order of ease of implementation: 1) Configure the intermediary manually in a similar fashion to the "predefined host" feature (requires some mechanism to fail over to skip the intermediary if there is some issue) 2) For automatic intermediary, have a simple checkbox to enable: - automatically detect which peers are in the same LAN/WAN - allow these locations to be named and/or manually assigned to the devices/peers (more UI) - automatically negotiate which local device will act as an intermediary