sjau

Members
  • Content Count

    17
  • Joined

  • Last visited

About sjau

  • Rank
    Member

Profile Information

  • Gender
    Not Telling
  1. The weekend is close... I guess I'll give it a test spin then
  2. Upgrade to 12.04? 10.04 is only supported for 1 more year on a server.
  3. The main problem I have is that it has been working for weeks and now it suddently doesn't anymore... ok, that works now. Thx
  4. So, where do I need to add credentials now? also to the file in .config? And shall I make both ports the same? Hmmm, I amended the .config/btsync/btsync-auto.conf with the credentials but still the python icon doesn't like it. I also set the same port in .btsync/config.json no luck though. looking again at the btsync-auto.conf I noticed all chages were overwriten.
  5. maybe that's also of use: ps aux | grep btsynchyper 30124 2.2 0.1 431204 29236 pts/16 Sl 12:00 0:00 python /usr/lib/btsync-user/btsyncindicator.py --config /home/hyper/.config/btsync/btsync-auto.conf --iconpath /usr/share/icons/hicolor/22x22/statushyper 30134 0.0 0.0 4444 368 pts/16 S 12:00 0:00 /bin/sh /usr/lib/btsync-user/btsync-starterhyper 30161 93.7 0.5 445608 85208 ? Ssl 12:00 0:09 /usr/lib/btsync-user/btsync-agent --config /home/hyper/.config/btsync/btsync-auto.confhyper 30232 0.0 0.0 13236 920 pts/17 S+ 12:00 0:00 grep --color=au
  6. cat .btsync/btsync-user.log 2014-02-25 11:46:36+01:00 btsync-starter: start2014-02-25 11:46:36+01:00 make_user_files: User specific files and directories created2014-02-25 11:46:36+01:00 start_frontend: begin2014-02-25 11:46:36+01:00 start_frontend: frontend not running but LOCKFILE detected! Strange! btsyncindicator should handle it2014-02-25 11:46:36+01:00 start_frontend: starting frontend with default config file /home/hyper/.config/btsync/btsync-auto.conf2014-02-25 11:46:36+01:00 start_frontend: process is NOT running!!!! Something went wrong!2014-02-25 11:46:36+01:00 start_frontend: end20
  7. no it doesn't work.... no matter how long I keep it running, there's the exclamation mark in the systemtray icon and the warning above just keeps appearing. Tried to access the wui anyway but no luck. 2014-02-25 11:40:15+01:00 btsync-starter: start2014-02-25 11:40:15+01:00 make_user_files: User specific files and directories created2014-02-25 11:40:15+01:00 start_frontend: begin2014-02-25 11:40:15+01:00 start_frontend: frontend not running but LOCKFILE detected! Strange! btsyncindicator should handle it2014-02-25 11:40:15+01:00 start_frontend: starting frontend with default config file /home
  8. Did you add a new version to the repo yet? I just apt-get update && apt-get dist-upgrade but I didn't get a new version. Also, you said that this problem occurse only on old version like 12.04 but I'm running 14.04 and having the same issue. Get:1 http://debian.yeasoft.net/btsync/ trusty/main btsync-user all 1.14.2-1 [41.9 kB] :~$ btsync start:~$ BitTorrent Sync forked to background. pid = 12695WARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error message
  9. EDIT: CAN BE CLOSED - I JUST NEED TO READ THE FAQ MORE OFTEN. Hi there I have a question relating to .!sync files. What exactely are they? I noticed that they sometimes get created (and never deleted). So I wondere if I just could find . -type f -iname '.!sync' -exec rm {} \;
  10. You seem to misunderstand the term "two-way synchronization". one-way sync: MASTER --> SLAVE two-way sync: NODE <--> NODE From Wikipedia: In one-way file synchronization, also called mirroring, updated files are copied from a 'source' location to one or more 'target' locations, but no files are copied back to the source location. In two-way file synchronization, updated files are copied in both directions, usually with the purpose of keeping the two locations identical to each other. A bit late but still opting BTSync to go FLOSS