![]() start-stop-status start within the /var/packages/btsync/scripts/ directory and see what happens. If the service still won't start, try launching it through the root-SSH console, by simply running. However, simply reset the permissions of this folder as shown before and everything should be okay again. #BITTORRENT SYNC 1.4 UPDATE#It depends on whether the update will remove and re-create this folder or just leave it as. Actually I don't expect BitTorrent to change a lot within this script, meaning that you should be able copy away your version of the script before updating and then copy it back afterwards, without running into any issues.Īnother thing that could happen is a permission reset on the /usr/local/btsync/var/-folder. The Downside (yes, unfortunately there is one)Īs soon as a new update for the BitTorrent Sync package will be available, the modified start-stop-script will probably get overwritten with the package's script. Each user can then connect to the btsync webui using your Synology's IP/hostname and the port you specified in the "" file (For example: 192.000.0.0:9991). Your data is your data alone and you deserve to choose where it is stored, whether it is shared with some third party, and how its transmitted over the internet. It synchronizes files between two or more computers in real time, safely protected from prying eyes. Using ps | grep btsync you should be able to confirm that there will be multiple btsync processes, ran by the users you specified. Syncthing is a continuous file synchronization program. Then specifiy a btsync webui "login" and "password", replacing "enter here".Īfter completing all these changes, login to your Synology NAS web-interface as admin and run the BitTorrent Sync service. So for user1, this would be 9991, for user2, 9992, etc. Multiple updates followed, including versions 1.1, 1.2, 1.3, and 1.4. "pid_file" : "/usr/local/btsync/var/syncapp-user1.pid",Įnter your correct IP/hostname, replacing "192.000.0.0".Īlso make sure that every user uses a different "listen"-port for the webui. BitTorrent first introduced Sync in April 2013 to let users share folders and files without having to rely on a cloud service. "storage_path" : "/volume1/btsync/user1", Then, I changed permissions to the /usr/local/btsync/var/ folder, so that every user is able to create a pid-file: **Make sure the BitTorrent Sync service is turned off before! Next, I overwrote the package's original script at /var/packages/btsync/scripts/start-stop-status with my version, by connecting to my NAS through SSH, as "root" (Using ssh – more info). All users that should run their own btsync process have to be added (space-separated) there. The script contains of a variable named USER. You can find an up to date version of it within this repository. Now, here's what I did to solve this issues:įirst, I modified the BitTorrent Sync init.d-script ("start-stop-script"). Besides, each user should be allow to use their very own version of the WebGUI, to configure sync directories and retrieve access codes. This makes it impossible to write data into other user's home-directories (at least, if they're configured in a safety-conscious way -)). The BitTorrent Sync default installation on a Synology NAS creates a "btsync" user that runs the homonymous service. Unfortunately the people behind the Synology community package didn't put as much love into it as it would deserve. BitTorrent's Sync service (btsync) is a great tool which, in combination with a Synology allows you doing fancy things. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |