tuxpoldo
-
Posts
730 -
Joined
-
Last visited
-
Days Won
27
Everything posted by tuxpoldo
-
Thank you for the report. It will be fixed in the next release! -
Updated all packages to 1.1.27 - All Debian builds are now online. Ubuntu builds are on the way and should be online in a few minutes.
-
Updated all packages to 1.1.27 - All Debian builds are now online. Ubuntu builds are on the way and should be online in a few minutes. Changelog: btsync (1.1.27-1~sid) sid; urgency=low * New upstream release -- Leo Moll <leo.moll@yeasoft.com> Thu, 04 Jul 2013 16:59:15 +0200
-
Hey Guys! Please read the doc. With the server packages, you have the option to create many BTsync instances running under specific user credentials. The default instance created by the server packages always runs as root but you can create additional or alternative instances (if you do not let debconf create a default instance -> first question) running under different credentials. Read the doc. Read the doc. READ THE DOC. less /usr/share/doc/btsync/README.Debian btsync for Debian ----------------- This version of BitTorrent Sync is mainly intended for server usage. It allows to start one or more BitTorrent Sync daemons based on configuration files located in /etc/btsync Configuration parameters not parsed by btsync but by the daemon scripts can be supplied as comments in the configuration file. The following parameters are supported: DAEMON_UID: A uid for supplying the user under which the btsync daemon should run DAEMON_GID: A gid for supplying the group under which the btsync daemon should run. If omitted the daemon will run under the primary group of the user DAEMON_UMASK: The umask for the btsync damon. If omitted the default umask is used. The parameter definition must use an equal sign ("="): // // DAEMON_UID=jdoe // DAEMON_UMASK=0002 // This example will launch the instance running under the credentials of the user "jdoe" using 0002 as umask The old mechanism using the encoding in the configuration file name following the naming scheme <damon name>[.<user>[.<group>]].conf is still supported but is superseded by data supplied in the configuration file itself. Support may be dismissed in future releases. By specifying <user> and <group> it is possible to specify under which credentials the daemon runs. In this case it must be assured that the daemon is able to write into the data directory specified in the configuration file. Some example files are provided under /etc/btsync/samples The file /etc/default/btsync allows to configure the way the daemon starts: The variable AUTOSTART defines which daemons are started automatically. It can assume the values none No daemon is started automatically all (default) All daemons are started automatically <list> Only the specified daemons are started automatically The variable DAEMON_ARGS allows to specify additional commandline parameters passed to the daemon. And if you are using btsync as the only user on a desktop machine, please take in consideration installing the desktop version because it is really more suitable for your use case: the desktop version works like the windows or mac version. A btsync instance is autostarted on user login (obviously running only in the user context). sudo apt-get install btsync-user
-
Unfortunately not. I asked the developers, but up to now I got no answer... :-( We are discussing about this. As soon as I know something new, I will let you know.
-
Updated all packages to 1.1.26 - All Debian builds are now online. Ubuntu builds are on the way and should be online in about 15 minutes.
-
Updated all packages to 1.1.26 - All Debian builds are now online. Ubuntu builds are on the way and should be online in about 15 minutes. Changelog: btsync (1.1.26-1~sid) sid; urgency=low * New upstream release -- Leo Moll <leo.moll@yeasoft.com> Wed, 03 Jul 2013 22:20:42 +0200
-
Sorry! Packages for Debian are online. Packages for Ubuntu should be in about 15 minutes...
-
You only have to create a suitable configuration file in /etc/btsync - all other stuff is in place. Please take a look at the documentation in /usr/share/doc/btsync
-
gpg can use different protocols to retrieve keys. HTTP is one, but there is also a direct keyserver protocol that uses port 11371. The error message you got, suggests that HTTP was used as protocol... The first question asked you, if you want to define a default BitTorrent Sync instance. That means: debconf asks you a series of questions, and than it creates a configuration file for a default instance for you. This file is maintained by debconf and should not be edited manually. You can modify the configuration settings by executing the command sudo dpkg-reconfigure btsync Anyway you can add additional configuration files if you want to run more than one instance of btsync on a machine. The only reason to do that, usually is to have btsync to run under different user credentials. Something must be wrong with your terminal window size.... For most people, creating the config file via debconf would be OK. But if you do not want a web gui, you must create your own configuration files manually. In this case, answering "No" to the first question, is the right choice. In order to create configuration files, you should look at the samples - especially at /etc/btsync/samples/complex.conf - a fully commented version. For all other questions reguarding the functionality of btsync, you should post your questions in separate topics of the forum, since this topic is only related to the debian packaging itself.
-
No. From here it works. But look at the error message: gpg: requesting key 6BF18B15 from hkp server pgp.mit.edu ?: pgp.mit.edu: Connection timed out gpgkeys: HTTP fetch error 7: couldn't connect: Connection timed out And now try to navigate to: http://pgp.mit.edu If you can reach it, also gpg --keyserver pgp.mit.edu --recv-keys 6BF18B15 should work. If not, you have a generic connection problem to pgp.mit.edu. There may be several reasons for this: Sometimes websites are offline if they have problems with the hardware. This is only a temporary error Maybe the route from you to them is offline because of a failure in one of the routing sites. Also this is only a temporary failure Maybe you live in a country in which cryptography is forbidden and the government blocks access to sites with potential cryptographic content. Basically also this is a temporary failure, if people elects a different government or people starts a revolution ;-)
-
You are right. I made now some extensive tests, and I verified that btsync does something strange into the replicated folders. But let's start at the beginning: basically the feature works. Let's remember: the umask defines the bits that are masked out before creating a file/directory. That means: the standard library sets 777 as permissions for directories and 666 as permissions for files. Filtered by the default umask, this results in 755 and 644. Basically this seems to work with btsync. If I look at the logfile (/var/lib/btsync/sync.log) I get exactly the permissions I expected: with umask 0022: yeasoft-gate2 /mnt/data/btsync-areas/leo # ls -la /var/lib/btsync/sync.log -rw-r--r-- 1 root root 264 Jun 30 13:10 /var/lib/btsync/sync.log with umask 0002: yeasoft-gate2 /mnt/data/btsync-areas/leo # ls -la /var/lib/btsync/sync.log -rw-rw-r-- 1 root root 264 Jun 30 13:12 /var/lib/btsync/sync.log with umask 0000: yeasoft-gate2 /mnt/data/btsync-areas/leo # ls -la /var/lib/btsync/sync.log -rw-rw-rw- 1 root root 264 Jun 30 13:15 /var/lib/btsync/sync.log The problem can be viewed in the replicated files: with umask 0000: yeasoft-gate2 /mnt/data/btsync-areas/leo/test # ls -la total 16 drwxr-xr-x 3 root root 4096 Jun 30 13:30 . drwxr-xr-x 11 root root 4096 Jun 30 13:30 .. drwxr-xr-x 2 root root 4096 Jun 30 13:30 testumask0000 -rw-rw-r-- 1 root root 5 Jun 30 13:29 testumask0000.txt with umask 0002: yeasoft-gate2 /mnt/data/btsync-areas/leo/test # ls -la total 24 drwxr-xr-x 4 root root 4096 Jun 30 13:33 . drwxr-xr-x 11 root root 4096 Jun 30 13:30 .. drwxr-xr-x 2 root root 4096 Jun 30 13:30 testumask0000 -rw-rw-r-- 1 root root 5 Jun 30 13:29 testumask0000.txt drwxr-xr-x 2 root root 4096 Jun 30 13:33 testumask0002 -rw-rw-r-- 1 root root 5 Jun 30 13:32 testumask0002.txt with umask 0022: yeasoft-gate2 /mnt/data/btsync-areas/leo/test # ls -la total 32 drwxr-xr-x 5 root root 4096 Jun 30 13:35 . drwxr-xr-x 11 root root 4096 Jun 30 13:30 .. drwxr-xr-x 2 root root 4096 Jun 30 13:30 testumask0000 -rw-rw-r-- 1 root root 5 Jun 30 13:29 testumask0000.txt drwxr-xr-x 2 root root 4096 Jun 30 13:33 testumask0002 -rw-rw-r-- 1 root root 5 Jun 30 13:32 testumask0002.txt drwxr-xr-x 2 root root 4096 Jun 30 13:35 testumask0022 -rw-r--r-- 1 root root 5 Jun 30 13:34 testumask0022.txt What we see here is, that the umask feature works perfectly. None of the created files and directories contains masked out bits. But what we see here, shows also, that btsync does not create files and directories with standard permissions, but manipulates the permissions. My theory is: btsync always creates directories with 0755 and for this reason, an umask of 0002 or 0000 does not change anything btsync always creates files with 664 and for this reason, only an umask of 0002 or 0000 changes something.... Hey BT Developers: any clues?
-
Raspbian wheezy is an excellent choice. I'm only wondering, that lsb_release is not included. It is part of the default packages installed by every debian... Very strange. I have also a Raspberry Pi with raspbian installed (I use it to build the packages), but I've not tested if lsb_release is included... Anyway... now it works and this is the most important thing ;-)
-
Updated all packages to 1.1.22 - All Debian builds are now online. Ubuntu builds are on the way and should be online in about 1-2 hours.
-
Updated all packages to 1.1.22 - All Debian builds are now online. Ubuntu builds are on the way and should be online in about 1-2 hours. Changelog: btsync (1.1.22-1~sid) sid; urgency=low * New upstream release - Added support for specifying the credentials in the configuration file using DAEMON_UID=xyz and DAEMONGID=xyz in the comments - Added support for specifying the umask in the configuration file using DAEMON_UMASK=nnnn in the comments - Added debconf support for specifying the umask -- Leo Moll <leo.moll@yeasoft.com> Sat, 29 Jun 2013 16:17:11 +0200 All the new configuration optios are not visible during initial setup (since it is only fine tuning). If you want to change these options, you have to do a sudo dpkg-reconfigure btsync The umask feature was inspired by acmodeu: His idea to put the information in the configuration file, did not work, since btsync does not accept unknown variables there, but inspired me to find a solution to this problem and also to improve the user and group specification. Furthermore there is now a possibility to add more configuration parameters in the future...
-
Strange, but true. It seems that your installation of debian wheezy does not contain the command lsb_release. This should not be, since lsb_release is part of the base file layout of any debian (and not only...) system. If you are really sure, that "wheezy" is the name of your release, you can also enter it manually: echo deb http://debian.yeasoft.net/btsync wheezy main contrib non-free >> /etc/apt/sources.list.d/btsync.list But if your debian is so different (or broken) that tehre is no lsb_release, it is likely that you will encounter more problems when trying to run btsync...
-
Mhhh. There is no straightforward way to achieve this... But it's an interesting question. I see that the umask can be passed to the start-stop-daemon command responsible for launching btsync in the startup script... I will think about the possibility to configure additional parameters perhaps with a sidecar-configuration file.... Stay tuned.
-
Hi Andy! Great and thank you a lot! I will prepare a package for you containing the latest versions of all scripts and a description during the next day.
-
Then you have to create the config file manually and obviously you have the total freedom in tweaking it as you like. The first question that debconf asks, when installing btsync, is if you want to create a default instance. If you answer "No", than debconf does nothing and you have the total freedom. The option to create a default instance is intended for normal users that do not have special requirements.
-
Great! Creating good packages requires also a good knowledge of the target platforms. I've also started reading some documentation on how to build packages for Fedora, but the main problem is that I do not know so much about the inner workings of Fedora/RHEL/Centos/Suse(Bleah!) Basically the deployment is probably very similar (Init Script in /etc/init.d, the location of the startup configuration file /etc/default/btsync, is probably different and also the default locations for documentation, config files, data files are different. In addition I was not able to discover, if there is a mechanism similar to debconf...
-
Thank you for the report! The problem was an error in the firewall configuration (forgot to make the web server rules permanent). Now the site is reachable also via IPv6. Sorry for the inconvenience. I'm adding IPv6 to all my servers in the datacenter but I'm still learning ;-)
-
You will not find these settings in the Web UI. But if you are using my latest Debian Packages for Server use (btsync) and you have choosen to let debconf create a default instance, you can now set this parameter (and all other advances parameters) with sudo dpkg-reconfigure btsync
-
Nowadays we have installation packages for debianoid distributions, but I suppose that there is also a need for RPM packages (RHEL, Centos, Fedora, etc.). Since I have no experience in creating such packages, I would ask the community, if there is someone here able to make the same work I made for Debian/Ubuntu/Mint and willing to cooperate in creating these packages. From my part I can offer: The scripts and the concept of deployment Hosting space for the repositories in order to keep all together Any volunteer here?
-
OK - now I understand your needs behind the idea of making the data path configurable. Adding the data path as a configurable parameter is not so simple as for the other parameters, since there are a lot of eventualities to keep in consideration: If you offer a debconf based configuration, you should be aware of the fact that not every user is an advanced user (sysadmins prefer to do everything on their own ;-). So you must make sure, that all data entered is tested for consistency as much as possible Since you can change these parameters also after the installation (using dpkg-reconfigure) you must handle also the situation where an already existing data directory has to be moved to a new location with all error possibilities this may imply... The solution with the sybolic link is indeed a quite usual way to solve "hardcoded" paths, but in any case I will think about also adding the possibility to reconfigure the path...
-
sudo rm -rf /var/lib/btsybc sudo ln -s <wathever_the_dir_you_want> /var/lib/btsybc Something like this... But perhaps in the next release...
