jake.sadie

Members
  • Posts

    40
  • Joined

  • Last visited

  • Days Won

    3

jake.sadie's Achievements

Advanced Member

Advanced Member (3/3)

  1. Many years ago I set up a BitTorrent sync as the solution of choice for our research group to sync/backup individual user files to the server. I used a solution similar to the one described here (https://www.8layer8.com/?p=1082) to create config files for each user which pointed to their individual sync directories. The config files would include hard-coded directory keys. Each user would then connect to these folders with their keys in order to simply backup their data onto the server. With the move to Resilio Sync, I haven't seen any documentation around using this method (or something similar) to achieve the same end goal. Has anyone had success in implementing multiple instances for different users on their server?
  2. Hi Helen, Yes, it was related. I was able to get things installed but I still cannot get the service started. Any suggestions? Would you prefer we take this discussion to the other thread?
  3. Hi dh250, I just installed on my raspberry pi and cannot seem to get the service started. can you (or someone else) help explain what you did to get it going after you had your initial trouble? I keep getting an error telling me that No /usr/bin/btsync found running whenever I try to stop/restart the program. Thanks!
  4. womp - problem solved. got rid of that outdated package that came from before I installed using your script. all better!
  5. Hey Moe, Trying to shift over to the official repository after some time and I'm running into some issues moving away from your script. Any chance you can help me out? I deleted all of the files and directories listed in your remove command and set up the repository per the instructions from the blog post you linked, but installing results in the error shown in the image below. I'm trying to hunt down where the bittorrent-sync-pi-sewver 2.2.2 directory might be, but cannot find it... Any help greatly appreciated.
  6. FYI, been using this script since ~2.2.5 and it works great. Thanks!
  7. Just a follow-up for you. I have now installed this on two raspberry pis with non-default usernames and can confirm that taking these steps were necessary for the install to complete successfully: Edit btsync.sh to update to username I want to use to <user>Run btsync.sh to complete installEdit /etc/btsync/config.jsonLine 7: change <user>d to pidLine 7: change /home/pi/.btsync.... to /home/<user>/.btsyncLine 10: updated port number to reflect port number I was previously using (not necessary for everyone)Edit /etc/init.d/btsyncLine 21: change /home/pi/.btsync/data to home/<user>/.btsync/dataLine 25: change /home/pi/.btsync/data/.syncstream to /home/<user>/.btsync/data/.syncstreamLine 41: change db<user>d to dbpidLine 42: change "$db<user>d" to "$dbpid"Line 43: change "Stop<user>ng..." to "Stopping..."Line 49: change db<user>d to dbpidLine 50: change "$db<user>d" to "$dbpid"Line 53: change ...(<user>d $db<user>d)" to ...(pid $dbpid)"Again, not really a big deal to figure out, and thanks so much for doing this! Just so you know, my primary use case is I have two raspberry pis with large HDDs hooked up, one on the west coast where I live and one on the east coast at my mom's place. I have both running as backup servers for my family so there are two places data is backed up. I normally run multiple accounts/processes on each, one per family member. I previously wrote config scripts for each person, left them in the /etc/btsync folder, and the original init.d script back in the alpha/beta days would auto-load each whenever the process started. I'm not sure if this init.d script will do the same. Might be a nice thing to add, though I am guessing it is likely a feature that will help such a smaller user base that you might want to omit it. Just a thought.
  8. Hmmm, so I tried to accomplish this with a new folder pair. Computer A and B are both linked to my Pro License with the same username/key. I made a new advanced folder on computer A, setting it as the owner. It showed up on Computer B, as expected. I connected it, but it is default Owner with R/W access. I want computer B to merely be a backup server. I feel like the Pro version should allow both user-based and device-based access...
  9. I may have missed this long ago, but any way to change a folder from standard to advanced? I was living on 1.4.111 until 2.2 was released. Now I'm trying to update everything and I'd love to take advantage of this feature (I have a Pro license).
  10. installed but init.d script doesn't seem to be working for me? things I changed: I had to change my user name in the script to match my current user name. i changed the config.json to simply change the port number, so there should be no issues there. installed without errors after that point. now running the start command produces the echo output properly, but the service does not actually start. running the status command confirms that the service is not running. any ideas? learning more.... removing the --quiet and -b option from the start-stop-daemon command in the init.d script, i now can produce an error output: " Error while parsing config file: Invalid key 'jaked_file' " My config.json file says jaked_file should be: 'home/pi/.btsync/data/.syncsystem/btsync.pid' which means I have found at least one error. The config.json file needs to auto-update that line to include the proper $BTSYNC_USER if the person installing this changes the user from 'pi'. Manually changing this to '/home/jake/.btsync/data/.syncsystem/btsync.pid' still does not do the trick, unfortunately. Got it. VERY unfortunately, it appears that whenever you wrote the script to swap out the default username 'pi' with the intended username, 'jake' in my case, all of the lines with 'pi' anywhere in them were swapped with 'jake' that means all of the 'pid' variables turned into 'jaked' variables, which i had to change back manually. maybe there is a cleaner way to write the script to swap out from the default user being pi? regardless, thanks so much for writing this and putting it together! very helpful.