krychek

Members
  • Content Count

    13
  • Joined

  • Last visited

  • Days Won

    1

About krychek

  • Rank
    Member
  1. Why is this problem considered "solved"? It's just "workarounded". It's not possible to update BTSync when there is a non-admin user who's using it. Every time he starts BTSync after an update it will keep asking for admin password. Even if you provide it it won't stop asking for the password unless you make that user admin and then you can finish the update.
  2. I have the same problem with Btsync 1.4.103 on a DLink NAS. It's just not syncing after upgrading to 1.4 from 1.3.
  3. tuxpoldo: There you go: cat /var/log/dpkg.log | grep 2014-09-03 | grep btsync: http://pastie.org/9526502 I was messing around with it trying to fix it so there are a couple of removes and installs.
  4. I'm having a problem on two Ubuntu 14.04 boxes after the latest btsync update: hostname$ btsync starthostname$ BitTorrent Sync forked to background. pid = 8506. default port = 8888WARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error message I also have an exclamation mark in the btsync icon and and error message: Communication Error 400. Is this a known issue? I was able to fix it by removing btsync* and reinstalling it from the yeasoft PPA.
  5. I'm having a problem on two Ubuntu 14.04 boxes after the latest btsync update: hostname$ btsync starthostname$ BitTorrent Sync forked to background. pid = 8506. default port = 8888WARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error message I also have an exclamation mark in the btsync icon and and error message: Communication Error 400. Is this a known issue?
  6. So what is the proper signal? Is "killall btsync" proper?
  7. And how graceful is it to stop btsync by killing it? Won't it damage it in some way? Why doesn't it have a stop argument?
  8. The current use case of btsync for linux users is the following: They are unaware of the difficulties of the advanced configuration so the start the easy way and they configure everything in the Web UI. Later on they realize they need to make an advanced configuration. This is when they realize that all their previous work was in vein because they need to run --Dump-Sample-Config and do every configuration all over again manually in the config file. Their previous settings will be lost. This is not even documented. This is a very cumbersome procedure and not like any other linux daemon that use config files for their settings. Suggestions to improve the documentation (easy way): - Warn users in the user guide that they shouldn't do any configuration in the Web UI unless they don't want to do any advanced configuration later on. (See the next bullet point.) - Warn users in the user guide that starting btsync with a config file will erase their previous configurations they made in the Web UI. Suggestions to improve btsync (hard way): - Make an editible config file that is in sync with the configuration made in the Web UI. So it could be changed in both the Web UI or manually in the config file itself for advanced configuration. OR - Lose the config file altogether and make it possible to make any configuration in the Web UI.
  9. So I will lose my configuration... This is not very user friendly wouldn't you agree?
  10. That's exactly my problem. There is no editible config file present. You configure everything in the web app and once you have to change something advanced how do you do it? Dump the sample config file and start everything all over again from scratch? All your previous configurations lost? It doesn't make any sense right now.
  11. If there was an editable current config file why would anyone dump a sample config file?
  12. From the user guide: "Config file offers a slightly wider variety of options to configure. It is a JSON format file. In order to set preferences using a config file, first get a sample config by running --dump- sample-config. You’ll see a list of options and commentary." There is no mentioning of any current config file! Where is the current config file? I'd like to set the vaule of sync_trash_ttl. Contents of my .btsync directory: indicator.lock settings.dat sync.dat sync.lng webui.zip running settings.dat.old sync.dat.old sync.log settings.dat... it's a binary file, uneditable.
  13. Hey guys! I'm running btsync on a NAS (arm linux). I've configured many sync directories and other settings in the web gui but now I want to change an advanced setting (sync_trash_ttl). According to the user guide I have to run btsync with --dump-sample-config to get a sample config file and set sync_trash_ttl in it. But do I have to set everything else too??? Will I lose all my other settings if I start btsync with the newly generated config file?? Do I have to start the configuration all over again? This is not explained anywhere. Why isn't there a --dump-actual-config option? Why is there no config file when you first start btsync? I love btsync but this particular thing is not very well documented and/or very stone age solution. Btsync user guide: http://btsync.s3-website-us-east-1.amazonaws.com/BitTorrentSyncUserGuide.pdf