tuxpoldo

Members
 View Profile  See their activity

  • Posts

    730

  • Joined

  • Last visited

  • Days Won

    27

 Content Type 

Everything posted by tuxpoldo

  1. tuxpoldo
    Please give me more details! I tested it here both on my i386 and amd64 machines and it worked perfectly. Which platform? Which error message when trying to start manually by invoking it directly on the command line: sudo /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/debconf-default.conf
  2. tuxpoldo
    Released new btsync-common 1.2.67 upstream package. All packages are online on debian.yeasoft.net and ubuntu.yeasoft.net - users served by the Launchpad PPA have as usual to wait a few hours for the packages being built.... btsync-common (1.2.67-1) unstable; urgency=low * New upstream release -- Leo Moll <leo.moll@yeasoft.com> Tue, 05 Nov 2013 16:18:01 +0100
  3. tuxpoldo
    Released new btsync-common 1.2.67 upstream package. All packages are online on debian.yeasoft.net and ubuntu.yeasoft.net - users served by the Launchpad PPA have as usual to wait a few hours for the packages being built.... btsync-common (1.2.67-1) unstable; urgency=low * New upstream release -- Leo Moll <leo.moll@yeasoft.com> Tue, 05 Nov 2013 16:18:01 +0100
  4. tuxpoldo
    No problem. The only thing I wanted, was to explain, what was the situation I found, the presumed motivation of the BitTorrent Developers and my motivation to decide to put the additional parameters regarding the startup into the configuration file. I think that it is a good thing to discuss about the inherent problems, and I would also like to find a better solution. Unfortunately I'm not in the position to do anything regarding the format of the configuration file. Perhaps you have any Idea, what I can do to improve the overall experience? p.S.: I'm not a BitTorrent developer. I say this because I noticed that a lot of people thinks so....
  5. tuxpoldo
    Great! Thank you very much - I transferred to strings to GitHub - they will be included in the next release.
  6. tuxpoldo
    I think that the biggest problems with the JSON file are basically two: The format is very very strict. One wrong comma or parenthesis, and nothing works any more The parser unfortunately returns error messages that make it really difficult for the user to find what is really wrongI think that the developers have not spent very much time in this part of the software, since the main usage (Windows and Mac) does not require users to write a configuration file in order to get a working installation. Internally the configuration file is probably only the serialisation of internal data structures that are subsequently maintained in the internal database (that's the reason you can start btsync also without any configuration file, since there are decent defaults for standard user centric operation (but only if the executable is always started from the same directory). That's the reason I tried the help the user as most as possible NOT to deal with the configuration file... but since the UID/GID stuff has a lot of implications with user rights and accessibility, I preferred to leave the user in full control of it.
  7. tuxpoldo
    There are two internal files and a directory of btsync that are stored in the root of any shared folder: .SyncID.SyncIgnore.SyncArchiveYou must make sure, that btsync will be able to access all of them. If you have launched btsync initially as root, these files/directories have been created as root. Before switching to user mode operation, you MUST MAKE SURE, THAT EVERYTHING IS ACCESSIBLE AND WRITABLE. Please see the initial posting. Obviously it works. root can access everything. After that you should never start the daemon instance as root, because this will change the file permissions/ownership. Please try to really understand what you are doing, otherwise you will never get it running. Read carefully the initial posting: everything related to permissions is described there in detail.
  8. tuxpoldo
    I think that I'm the wrong person to discuss this. The configuration file format is defined by the developers of BitTorrent and they decided to use the JSON format (that is a totally standardised format like XML but length more concise and human-readable) with the very useful extension to permit comments. I see no reason to blame them for this decision. When writing my scripts for deploying and operating btsync on linux servers, I had to decide, if the additional instance related information would be stored in an additional configuration file per instance or embedded in the configuration file. Since the configuration file of btsync permitted to add comments, I decided to keep everything in one configuration file, that is the more practical solution. Everything is well documented (see initial posting).
  9. tuxpoldo
    Great! Thank you very much - I transferred to strings to GitHub - they will be included in the next release.
  10. tuxpoldo
    I have some news. Look here: http://forum.bittorrent.com/topic/24686-error-btsync-does-not-run-on-x86-compatible-geode-processors/
  11. tuxpoldo
    The solution to your problem is REALLY EASY: You have removed the comment slashes before DAEMON_UID and DAEMON_UMASK. If you had read carefully the initial posting, you would have seen the following phrase: "Configuration parameters not parsed by BitTorrent Sync but by the daemon scripts can be supplied as comments in the configuration file." Add the comment slashes before DAEMON_UID and DAEMON_UMASK and everything will work as desired. If you do not want to set the DAEMON_GID, remove the line.
  12. tuxpoldo
    Released new packages 1.1.82.1-3 with a few bugfixes and a fundamental change in the structure of the packages (the official components from BitTorrent Inc have been moved into a separate package that will be installed automatically). Both Debian and Ubuntu builds are online on debian.yeasoft.net - The Ubuntu builds on Launchpad will be probably available in 8-10 hours . If you are Ubuntu User and prefer to switch to the debian.yeasoft.com repository, you should delete the file tuxpoldo-btsync-precise.list in your /etc/apt/sources.list.d directory and follow the instructions in the initial posting. Changelog: btsync (1.1.82.1-3) unstable; urgency=low - The native upstream components from BitTorrent Inc. are no more included. All packages are now dependant upon the external package btsync-common which contains the btsync executables and documentation (Closes #18 and #19) - Fixed: The init script now tests on ARM systems if the btsync executable is compatible with the alignment handling and adapts it when needed (Closes #31 and #32) - Fixed: frontend was not be stopped on update in btsync-user (Closes #20) - Fixed: handling of update and remove of btsync-user is now working as expected (Closes #22) - Fixed: made initial installation less sensible against startup errors - Added German translation to debconf templates (Closes #23) - Added Italian translation to debconf templates contributed by Leo Moll and Andrea Pennelli (Closes #24) - Added French translation to debconf templates contributed by Quentin Scouflaire (Closes #25) - Added Russian translation to debconf templates contributed by dimitriy5181 (Closes #27) - Added Dutch translation to debconf templates contributed by Andras Kiss (Closes #28) - Added Hungarian translation to debconf templates contributed by Andras Kiss (Closes #29) - Added Czech translation to debconf templates contributed by Marek Lukas (Closes #30) - Added Greek translation to debconf templates contributed by Thanos Papaoikonomou (Closes #33) - Added Catalan translation to debconf templates contributed by VCLL (Closes #34) -- Leo Moll <leo.moll@yeasoft.com> Thu, 31 Oct 2013 14:57:49 +0100
  13. tuxpoldo
    Released new packages 1.1.82.1-3 with a few bugfixes and a fundamental change in the structure of the packages (the official components from BitTorrent Inc have been moved into a separate package that will be installed automatically). Both Debian and Ubuntu builds are online on debian.yeasoft.net - The Ubuntu builds on Launchpad will be probably available in 8-10 hours . If you are Ubuntu User and prefer to switch to the debian.yeasoft.com repository, you should delete the file tuxpoldo-btsync-precise.list in your /etc/apt/sources.list.d directory and follow the instructions in the initial posting. Changelog: btsync (1.1.82.1-3) unstable; urgency=low - The native upstream components from BitTorrent Inc. are no more included. All packages are now dependant upon the external package btsync-common which contains the btsync executables and documentation (Closes #18 and #19) - Fixed: The init script now tests on ARM systems if the btsync executable is compatible with the alignment handling and adapts it when needed (Closes #31 and #32) - Fixed: frontend was not be stopped on update in btsync-user (Closes #20) - Fixed: handling of update and remove of btsync-user is now working as expected (Closes #22) - Fixed: made initial installation less sensible against startup errors - Added German translation to debconf templates (Closes #23) - Added Italian translation to debconf templates contributed by Leo Moll and Andrea Pennelli (Closes #24) - Added French translation to debconf templates contributed by Quentin Scouflaire (Closes #25) - Added Russian translation to debconf templates contributed by dimitriy5181 (Closes #27) - Added Dutch translation to debconf templates contributed by Andras Kiss (Closes #28) - Added Hungarian translation to debconf templates contributed by Andras Kiss (Closes #29) - Added Czech translation to debconf templates contributed by Marek Lukas (Closes #30) - Added Greek translation to debconf templates contributed by Thanos Papaoikonomou (Closes #33) - Added Catalan translation to debconf templates contributed by VCLL (Closes #34) -- Leo Moll <leo.moll@yeasoft.com> Thu, 31 Oct 2013 14:57:49 +0100
  14. tuxpoldo
    The x86 version of btsync for linux does not run on my ALIX router board. Details: tuxpoldo ~ # /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/debconf-default.confBy using this application, you agree to our Privacy Policy and Terms.http://www.bittorrent.com/legal/privacyhttp://www.bittorrent.com/legal/terms-of-useIllegal instructiontuxpoldo ~ # cat /proc/cpuinfoprocessor : 0vendor_id : AuthenticAMDcpu family : 5model : 10model name : Geode(TM) Integrated Processor by AMD PCSstepping : 2microcode : 0x8bcpu MHz : 498.027cache size : 128 KBfdiv_bug : nohlt_bug : nof00f_bug : nocoma_bug : nofpu : yesfpu_exception : yescpuid level : 1wp : yesflags : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnowbogomips : 996.05clflush size : 32cache_alignment : 32address sizes : 32 bits physical, 32 bits virtualpower management:
  15. tuxpoldo
    I think that you will find a good explanation on how to handle separate configuration files in the initial posting. Unfortunately the btsync configuration files do not support includes, but you can write some scripts that generate the dedicated configuration files for each user on the fly.
  16. tuxpoldo
    Good idea! I updated the initial post and supplied a more detailed description about how to handle instances running under specific user credentials.
  17. tuxpoldo
    First of all, thank you! What is an Instance? An Instance is one btsync process running with a specific configuration. With the btsync package, you are able to define one or more configuration files. Every configuration file results in a specific btsync process running with the parameters specified into his configuration file.
  18. tuxpoldo
    Great! Thank you very much!
  19. tuxpoldo
    I added Swedish and Mandarin to the project. You can now start your work at the PO Editor btsync-deb project. Thank you very much for your help!
  20. tuxpoldo
    I added Catalan to the project. You can now start your work at the PO Editor btsync-deb project. Thank you very much for your help!
  21. tuxpoldo
    Thank you very much! I noticed it yesterday and I have already checked it in in GitHub... Do you made any changes after yesterday, 4:00 PM?
  22. tuxpoldo
    Execute the following command as root user: /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/debconf-default.confand look at the error message you get. If you have created no default instance, you should replace the name of the config file with the name of your manually created config file.
  23. tuxpoldo
    Ok, my terminology was not totally correct. Currently there is no manual about the whole btsync-user stuff. I used the word "manual" only for the pun. What I meant was the documentation. All important facts about btsync-user are currently documented in the initial posting of the corresponding forum message http://forum.bittorrent.com/topic/19560-debian-and-ubuntu-desktop-packages-for-bittorrent-sync/ and in the installed README file. The included man page documents only the commands of the btsync control script. The included PDF is the official documentation of the btsync engine as provided by the BitTorrent developers. This is only a naked application without any deployment and visible UI and the documentation handles only functionality of the core application.
  24. tuxpoldo
    If you want to keep your own configuration file, it should be named btsync.conf and not .btsync.conf Read the fine manual ;-)
  25. tuxpoldo
    I added Japanese to the project. You can now start your work at the PO Editor btsync-deb project. Thank you very much for your help!