g2nightmare

Members
  • Content Count

    7
  • Joined

  • Last visited

About g2nightmare

  • Rank
    New User
  1. Just to clarify, btsync-gui is the same thing except supported? Is it up to date?
  2. I see that you updated the repositories (I think?) There are some bugs you may or may not be aware of. I used a clean install of Kali Linux (debian based) and did an install of btsync-user. Upon installing, the gui icon has an explanation point through it and says "Communication Error 500." Upon providing my secret key and restarting the machine, I always get a "communication error 401" on the gui. Weirdly enough, btsync actually runs. I ran it via terminal and I get something that says: blah blah forked to background (good) /usr/lib/btsync-user/btsyncindicator.py:138 warning at /tm
  3. Everything is the most recent version. The ARM version and the Windows version were downloaded from the website last night. The debian version I got through apt-get. I force checked for updates.
  4. I have this very weird issue. I have a netbook (with Debian), a raspberry pi (with ARM), and a desktop (with the windows client). I use the raspberry pi as a node, so that I can get an asynchronous connection between the netbook and desktop. When on the same network, my netbook is after to sync with my desktop AND my raspberry pi (my raspberry pi is NOT on the same network, but is able to locate it) When I'm on a different network (i.e. a school network with my netbook), I cannot locate my raspberry pi. I think this tells me that there is an issue with the school network blocking the dat
  5. Sorry I took so long to get back to this. I'll have to try what you suggested tomorrow and thanks for all of your work. I'm excited to get this to work. I had been using an alias in my bashrc to solve the problem.
  6. Has anybody gotten this to work on Fedora 18/19? I ended up using a script very similar to this: https://gist.github.com/ricco386/5467477 And added it to chkconfig using this: http://unix.stackexchange.com/questions/20357/how-can-i-make-a-script-in-etc-init-d-start-at-boot At startup, it appears to work. The problem is that 50% of the time, sync never gets forced, so I need to find a way to restart the service. Doing: service btsync stop says that it occurs, but upon checking "top," the process still runs and the service is never killed. It seems to me that killproc never actually reads