tuxpoldo

Members
 View Profile  See their activity

  • Posts

    730

  • Joined

  • Last visited

  • Days Won

    27

 Content Type 

Everything posted by tuxpoldo

  1. tuxpoldo
    Are you sure, you are writing about the server version? I do not really understand, what is happening on your machine. Which old config file? No config file is updated during the update process of the software...
  2. tuxpoldo
    With the current version of btsync-user, the management interface is not secured with any credentials unless you use a manual config file override (~/.config/btsync/btsync-user.conf) in which you can define credentials. Currently the package installer tries to create the following files in order to make sure, btsync is autostarted: /etc/xdg/autostart/btsync-agent.desktop /etc/xdg/openbox/autostart/btsync-agent.desktop /usr/share/autostart/btsync-agent.desktop /etc/xdg/autostart/btsync-agent.desktopAll those files are only symbolic links to the same file. You should try to delete them all but keep in mind, that on the next update they will be recreated. In any case I will take your wish as a feature request and I will implement a possibility for any user to not autostart it. See Issue #58 Please check that all config files are in place (look for ~/.config/btsync/btsync-agent.conf). Please try to start btsync on the command line with btsync restart First of all some words about the port number: in order to allow multiple users to have their own instances of btsync running on the same machine at the same time, every daemon is configured to use different ports. By default (if you have not defined any user defined config file), the port number for the web ui is computed with the formula 8999 + uid that leads generally to 9999 for the first user, 10000 for the second user, etc. I have no idea, why the startup of BitTorrent Sync and the indicator have problems on your machines. Please try manual restarts with the command line utility in order to see, if there are some meaningful error messages.
  3. tuxpoldo
    Are you using the Debian and Ubuntu Server Packages of BitTorrent Sync? If yes, you should consider changing the UMASK - you will find information about this in the initial posting.
  4. tuxpoldo
    I'm really wondering, what may be the difference.... The scripts basically do exactly the same thing: start-stop-daemon --start --quiet --chuid $USER --name $NAME --exec $DAEMON -- --config /etc/btsync.conf The only difference is the forking method. The script from http://bernaerts.dyndns.org/linux/75-debian/290-debian-server-btsync-permanent-peer delegates the daemonization to the btsync executable itself. The scripts from my debian packages delegate the daemonization of the btsync executable to the start-stop-daemon routine. I suppose that this may be the reason, since the process has slightly different characteristics. There was a reason for handling it this way (due to some particularity of btsync in the very first versions) but nowadays it could be also implemented in the other way. I would like to test a modified version of my package, but I have no OpenVZ environment with exectly the same characteristics. Would you be available for testing it?
  5. tuxpoldo
    Strange. According to the Linux Programmers Guide, signal 2 means SIGINT (Terminal Interrupt) - equal to pressing CTRL+C in a foreground application. I think that this is really a support case for the developers. Maybe it's a side effect of the virtualisation layer? Do you have any idea, which hypervisor or virtualisation system is used for your vServer?
  6. tuxpoldo
    Yes, you are wrong. The package btsync does not contain the BitTorrent Sync executable, but only all the stuff around it (like the init scripts, the configuration files, the readme files, the changelog, etc.) that is developed in a totally independent manner and therefore has it's own version number. This package depends upon the package btsync-common (installed automatically installed by the dependency management of the package management) which has the version 1.2.82-1. This package contains the BitTorrent Sync executable and is only updated when BitTorrent Inc. updates the package. If you log in on the web ui, you will see directly under the BitTorrent Sync logo the line: Version 1.2.82 ( up to date )
  7. tuxpoldo
    Some information for your convenience: The Debian/Ubuntu packages for Server usage (btsync) do not enable UPnP by default when creating the default instance (obviously on user generated config files, it's up to you). If you want to enable it, you have to execute dpkg-reconfigure btsync and enable it when asked. The Debian(Ubuntu packages for Desktop usage (btsync-user) enable UPnP by default for every user since this is the common home user scenario. If you do not want so, you have to modify manually the configuration file template or create a user defined configuration file.
  8. tuxpoldo
    Thank you very much for your efforts!
  9. tuxpoldo
    Hi Oliviakrk! The management of daemon autostart settings is completely managed by the Debian package manager and I can change it only by implementing a complete manual override of that (that's not really a good idea). But there is a standard solution for your use case. In order to avoid autostarting the btsync damon, you have to uncomment the line AUTOSTART="none" in /etc/default/btsync - this prevents all the daemons to be autostarted. In your cron-scripts, you should the use the following commands to start/stop the daemon: service btsync start debconf-default and service btsync stop debconf-default If you have not defined a default instance but you are running with a hand crafted configuration file, replace debconf-default with the name of your config file without the extension. I will answer your post in the Desktop Package Thread since it may be of interest also for other users.
  10. tuxpoldo
    OK - on my Ubuntu test machine it works. So before I start setting up a Debian test machine, I would kindly ask you to post here the currently active configuration file (if it contains credentials, please do not forget to substitute them with placeholders) and to try to invoke the Web UI by entering the URL http://127.0.0.1:9999/gui manually in a freshly started browser. If you still get in the browser no output, I suppose that the problem is more related to the running instance of btsync instead of the indicator. p.S.: The automatically created configuration file is ~/.config/btsync/btsync-auto.conf - if you override it by a manual created file, it should be ~/.config/btsync/btsync-user.conf
  11. tuxpoldo
    OK - sorry for this additional update, but I forgot some debug code in the previous versions. This debug code generates a strange file in the home directory of the user root. This file contains only the list of groups in the system, so you can safely delete it, if you find it ;-) Sorry again! btsync (1.2.2-3) unstable; urgency=low * Removed debugging log file forgotten during previous development -- Leo Moll <leo.moll@yeasoft.com> Mon, 27 Jan 2014 16:24:02 +0100
  12. tuxpoldo
    After a long time, I'm pleased to announce also a new version of the package for desktop usage. This package features a consistently improved support for pause and resume including persistence of the paused state across reboots, a totally redesigned cleaner and more compliant structure of configuration files (all configuration files are now stored in ~/.config/btsync), some bugfixes and a brand new version of btsyncindicator.py featuring improved protocol handling and several bugfixes. If you are running with a custom configuration file ~/btsync.conf it will be automagically moved into the new location (~/.config/btsync) and renamed to btsync-user.conf Changelog: btsync-user (1.13.0-1) unstable; urgency=low * New upstream release 0.13 of btsyncindicator - Improved pause and resume support - Fixed lots of problems with authentication - Fixed missing http error handling - Fixed keyerror when creating menu for read-only folders - Autologin support to the menu function "Open Web Interface" when creating menu for read-only folders) * Improved pause/resume support in btsyncindicator * The paused state is now persistent over reboots (Closes #12) * Reorganized the file structure in the home directory to make things more compliant and clean. All configuration data is now stored in ~/.config/btsync (Closes #55) * Better check to avoid that the indicator starts twice (Closes #50) -- Leo Moll <leo.moll@yeasoft.com> Mon, 27 Jan 2014 14:29:24 +0100 All builds on the YeaSoft Repository are already online. If you are using the launchpad repository, you have to wait a few hours, as ususal....
  13. tuxpoldo
    Minor fix version: btsync (1.2.2-2) unstable; urgency=low * Updated debconf localizations (Czech, Dutch, Galician, Hungarian, Spanish) * Fixed wrong warning about changed credentials -- Leo Moll <leo.moll@yeasoft.com> Mon, 27 Jan 2014 09:21:11 +0100
  14. tuxpoldo
    Since the package provides debconf support in several languages, every release with new features requires also some localisation efforts. Many people has helped in translating the debconf strings, but the more translators there are, the faster an up to date localised version can be released. There is still some work to do in order to support all the new features in the currently available languages, and it would be really nice, if more translators join these efforts. If you think you can help, consider joining the team at https://poeditor.com/join/project?hash=021de7da0c2a0562da16dfcefcb26cc1 Currently there are still some strings that have to be translated to Catalan, Chinese (simplified), French, Greek, Polish, Russian and Swedish.
  15. tuxpoldo
    After a long time, I'm pleased to announce a new version of the package for server usage. In addition to a bugfix for a quite ugly bug reported by Ephemeral in this post, there is a brand new feature requested by many users: the possibility to specify also full credential information for the daemon in the default instance managed by debconf. Enjoy this brand new release! Changelog: btsync (1.2.2-1) unstable; urgency=low * It is now possible to select arbitrary system users as credentials for running the btsync daemon * It is now possible to select arbitrary system group as credentials for running the btsync daemon (Closes #53) * Fixed malformed number formatting in default instance configuration file generation (Closes #56) -- Leo Moll <leo.moll@yeasoft.com> Sun, 26 Jan 2014 16:16:16 +0100 All builds on the YeaSoft Repository are already online. If you are using the launchpad repository, you have to wait a few hours, as ususal....
  16. tuxpoldo
    Sure there is a wishlist: Look! But obviously there is also an internal list of features that will be implemented. That's a standard procedure in development teams...
  17. tuxpoldo
    Great work!
  18. tuxpoldo
    Good news: the feature has been added in the official wish list ;-)
  19. tuxpoldo
    Unfortunately I know no way to achieve that. BitTorrent Sync allows only to bind the internal web server for the UI to a specific network interface, but not the engine itself. I would consider this a very useful change request.
  20. tuxpoldo
    Good idea. I will implement this together with another suggestion documented in Issue #55 Please check, if the file /etc/apt/sources.list.d/btsync.list has the following content: deb http://debian.yeasoft.net/btsync wheezy maindeb-src http://debian.yeasoft.net/btsync wheezy main On some systems the command for creating the file does not produce the desired results.
  21. tuxpoldo
    Thank you for the report. I was able to reproduce the problem by entering numbers with a leading 0 in the dialog boxes (I think you have done so). It will be fixed in the next release. In the meantime, invoke dpkg-reconfigure again and make sure you enter your values without leading zeroes. See Issue #56 on Github. If you like to discuss with other users using this package, you may refer to the Debian And Ubuntu Server Packages For Bittorrent Sync Thread in this forum.
  22. tuxpoldo
    I have no idea. I saw this happen a lot of times, and there are a plenty of users reporting similar issues totally unrelated to the linux version. From from my observation sometimes it helps to restart ALL btsync instances on all computers. If this does not help, you should stop btsync on the computer apparently synching indefinitely, and search for files with the extension similar .!sync in the replicated paths. You should then delete those files and afterwards restart btsync. In my case, this always solved the problem.
  23. tuxpoldo
    I suppose you installed the server version of the packages. During the installation, you were asked: You can choose, if you want BitTorrent Sync to run as root (not recommended) or under it's own unprivileged credentials (user: btsync, group: btsync). WARNING: If you change this setting in an already running instance, you must take care of changing the ownership of all files in the managed folder shares in order to make sure that BitTorrent Sync will still be able to access and modify them. By default the installer proposes to run the daemon with a dedicated unprivileged user. This obviously means, that the daemon has only access to files and directories readable for everyone. In addition the btsync daemon needs write access to all paths that will be included in the synchronisation. So basically there are several different approaches: If you plan to let btsync synchronise several directory trees belonging to different users but do not care who will be the owner or creator of a file, you should give the user "btsync" read and write permissions to all involved files and directories and make sure that the respective users will also be able to read and write the files created by the btsync daemon. There are several ways to achieve this and it may depend on the access rights method implemented in the file system (UNIX permissions, ACL, etc.) If you plan to let btsync synchronise several directory trees belonging to different users and you want btsync to behave exactly like the user (that means preserving ownership and permissions), you cannot use the default instance managed by the installer package, but you must answer "No" to the first question "Do you want to define a default BitTorrent Sync instance?" and then create an manually maintained instance for every involved user by creating a dedicated configuration file with DAEMON_UID and DAEMON_GID set to the relative user credentials. If you want only to replicate directory trees owned by the user "root", you should instead select to let the btsync daemon run under "root" credentials If you want only to replicate stuff in your home directory and your machine is a workstation, you are using the wrong package. Consider installing the package btsync-user instead of the package btsync. More information can be found here. I hope that this helps a little.
  24. tuxpoldo
    What is your definition of valid permissions?
  25. tuxpoldo
    I spent some thought on it in the last weeks and I'm thinking about it. The support of systemd would affect both packages (the server and the desktop one) but I would probably start with the server package. Can you tell me, how to switch a normal debian server system running with init to systemd?