tuxpoldo

It's amazing! I can see the live progress of localisation. Tajnymag is currently translating in Czech and he will finish in a few minutes... You are great!

I added Czech to the project. You can now start your work at the PO Editor btsync-deb project. Thank you very much for your help!

Thanks! I will transfer it to GitHub during the day...

I added Greek. You can now start your work at the PO Editor btsync-deb project. Thank you very much for your help!

You are right! Sorry. I forgot but it was logical: the daemon must at least be able to access his configuration file ;-) ....and since the file contains security relevant information (the access data to the web interface), it is always a good idea to make it owned by the uid and gid under which the btsync daemon runs AND limit the access rights to only that user (sudo chmod 400 /etc/btsync/acmodeu.conf). Don't worry. root will always be able to access the file...

Since you are asking in the server thread, I suppose you installed the server version of btsync. The behaviour of the server version is highly dependent upon what you specified to the debconf questions during the installation. For this reason it is not possible to give you an answer to your questions because there may be several configuration options that prevented you from accessing the web gui. I think it is better to ask you a fundamental question: Do you really need the server version? I have the impression that you are more a typical desktop user that wants btsync to run on its desktop linux machine. In this case you should uninstall the server version, install the desktop version and then logout and login again: sudo apt-get --purge remove btsyncsudo apt get install btsync-user After logging in, you should see the btsync indicator in the tray and you will have also some desktop shortcuts that permits you to launch the web UI. See the desktop thread for more clarifications: http://forum.bittorrent.com/topic/19560-debian-and-ubuntu-desktop-packages-for-bittorrent-sync/ In any case I give you the advice to read CAREFULLY the initial posting (since it contains a lot of information). Many problems and solution that people has encountered were discussed in the topic thread.

Believe me acmodeu: you have to. Obviously it works. Both the automatically created file as the file you would create manually are parsed by the same btsync daemon - so there is no reason, why it should not work. BUT: The next time btsync is updated or btsync is reconfigured with dpkg-reconfigure, all your changes are lost. And this will create also additional problems, since on the next start btsync will again start as root and will write files with different ownerships and permissions. And if you repair it (by readding DAEMON_UID and DAEMON_GID to the config file, perhaps it will not work any more, since btsync then tries to write on files that are owned by root, but btsync is not running as root any more.. BTW: Since the whole btsync daemon now runs with different credentials, you should have changed the ownership of /var/lib/btsync and all files in this directory - otherwise btsync will get in trouble when trying to write to his own internal database files. One question: When you opened debconf-default.conf in the editor, the first lines you should see are: //!/usr/lib/btsync/btsync-daemon --config//// Default instance automatically created by debconf//// DO NOT EDIT THIS FILE MANUALLY//// use dpkg-reconfigure btsync to modify the// configurationDo you think, "DO NOT EDIT THIS FILE MANUALLY" was a joke? You are not the only one, that was convinced, I was kidding. Look here: http://forum.bittorrent.com/topic/18974-debian-and-ubuntu-server-packages-for-bittorrent-sync/page-12#entry66632 In order to avoid such misunderstandings in the future, I improved the warning in the next version: // Default instance automatically created by debconf//// DO NOT EDIT THIS FILE MANUALLY - SERIOUSLY//// THIS FILE WILL BE OVERWRITTEN AT EVERY UPDATE// OR RECONFIGURATION SO DO NOT EVEN TRY IT//// USE dpkg-reconfigure btsync INSTEAD TO MODIFY// THE CONFIGURATION//The reason why you have to manage settings like DAEMON_UID in manually managed configuration files, is that the interactive configuration via debconf does not offer the possibility to specify those settings. There is a reason for this: The automated configuration via debconf is a help facility mainly intended to support less advanced users in getting a standard configuration without many efforts. If you want instead to tweak every possibility that the software gives you with the configuration file, you are an advanced user and you will not need such a facility. You have more freedom, but you have also more chances to break everything. Since debconf offers no simple way to ask for user credentials in a secure way (you can break so many things if you do not really understand the implications), this is considered an advanced feature. Advanced features are for power users, and power users prefer to edit their configuration files manually and not use GUIs that limit them in their freedom. Please do the following now: Stop btsync (sudo stop btsync)Since you are creating a separate instance of btsync, you should not use /var/lib/btsync as the storage_dir, since this directory is reserved for the default instance. Let's say that /var/lib/btsync-acmodeu will become your new storage_dir. Create it, and then move the contents (ONLY THE FILES settings.dat, settings.dat.old, sync.dat, sync.dat.old, sync.lng, sync.log, sync.pid, webui.zip) of /var/lib/btsync in /var/lib/btsync-acmodeuUnfortunately I noticed, that you messed up some things: you used /var/lib/btsync also to store replicated content (/var/lib/btsync/Archive). THIS IS A FATAL MISUNDERSTANDING! The storage_dir is the directory in which btsync holds its internal data. It is NOT an area for the user to keep his replicated content! In btsync you can decide in the configuration which folders shall be replicated and these folders can be everywhere.Change the ownership of the new storage directory and the files within to the uid and gid under which you want the btsync daemon to runMake a duplicate of the default configuration file by creating a copy (sudo cp /etc/btsync/debconf-default.conf /etc/btsync/acmodeu.conf)Open /etc/btsync/acmodeu.conf in an editor and do the following:Write something informative in the header (like: THIS IS ACMODEU'S VERY PERSONALIZED CONFIGURATION FILE) and remove the old header information. It is always a good idea to keep things well documented. Since the file is now maintained by you, it would be wrong to keep information like "this file is maintained by debconf"Change the storage_dir to /var/lib/btsync-acmodeuMake all changes you need (like adding DAEMON_UID and DAMON_GID)Invoke sudo dpkg-reconfigure btsync and answer immediately to the first question THAT YOU DO NOT WANT BTSYNC TO CREATE A DEFAULT INSTANCE.After that, the file /etc/debconf-default.conf should disappear and btsync will be restarted (with the instance defined by your personal configuration file. The most important thing, is that you understand exactly what you are doing: You will have a btsync daemon configurated by your very personal configuration file /etc/btsync/acmodeu.conf The daemon will run under specific credentials you have defined The daemon will store his internal database, state and helper files in /var/lib/btsync-acmodeu The directory /var/lib/btsync-acmodeu and all its contents are owned by the uid and gid under which the daemon will run The daemon must be able to access and write all the directory and files that are part of a replication set

One thing: you know, that you can let run btsync under different credentials? See DAEMON_UID and DAEMON_GID (read the initial posting). The only thing, is that this is currently not supported by debconf - that means: you must create and maintain your configuration file manually.

Mhh. Interesting. I think this effect is due to the fact, that btsync does not behave as other standard Linux applications when creating directories. Here is the standard behaviour: linux-dev-64 ~ # mkdir foolinux-dev-64 ~ # chown :www-data foolinux-dev-64 ~ # chmod g+s foolinux-dev-64 ~ # mkdir foo/barlinux-dev-64 ~ # touch foo/bar/newfile.txtlinux-dev-64 ~ # ls -la foototal 12drwxr-sr-x 3 root www-data 4096 Oct 22 17:47 .drwx------ 33 root root 4096 Oct 22 17:47 ..drwxr-sr-x 2 root www-data 4096 Oct 22 17:47 barlinux-dev-64 ~ # ls -la foo/bartotal 8drwxr-sr-x 2 root www-data 4096 Oct 22 17:47 .drwxr-sr-x 3 root www-data 4096 Oct 22 17:47 ..-rw-r--r-- 1 root www-data 0 Oct 22 17:47 newfile.txtYou remember? We had the same problem with the files. It was fixed after we reported the bug to the developers... I have reported the problem directly to the developers. Let's see if they are able to fix the bug.

Since you typed $wheezy instead of wheezy, you got a wrong output. The contents of btsync.list should be: deb http://debian.yeasoft.net/btsync wheezy maindeb-src http://debian.yeasoft.net/btsync wheezy main..and I do not understand, why you have three lines in this file, instead of two.

Many thanks to andrewid! The Hungarian translation is now complete and will be released within the next version!

I would say: it's because . does not have rws on the group part. Only .. has rws.

OK. Found you. But Since I planned a lot of reorganization work in the next weeks, it would be perhaps a better Idea to work in this phase with fork and pull requests...

Not really. I have btsync running on 3 of my servers in the data centre, and in server-server synchronisation it appears really fast, but I have no realistic data since in order to have a real life test setup, you need a lot of instances accessing concurrently and replicating a huge amount of changes in a huge amount of files. I think that currently it is too early to make such tests, since the application is still in beta and the developers still have not focused on performance. I think that with 1.20 we will see a lot of improvements regarding memory imprint and performance.

OK! Then please let me know. Now I already exported it and committed it to GitHub. I must update it as soon as you are finished...

Many thanks to the incredible knireis! He managed it to create the Dutch translation in world record speed!

Have you seen this?

Many thanks to dmitriy5181! The Russian translation is now complete and will be released within the next version!

I added Dutch. You can now start your work at the PO Editor btsync-deb project. Thank you very much for your help!

Done! Thank you!

This has already been reported in btsyncindicator as Issue #24. Since Mark is currently very busy, I suppose that it will take some days more than usual to have this bug fixed. This one is quite serious. Probably it would make sense to report it directly to the btsync developers.

I added russian. You can now start your work at the PO Editor btsync-deb project. Thank you very much for your help!

You're welcome! I added Galician and Brazilian Portuguese for you.

Great. The 13.10 Issue was already known. There is an open issue on this... This is really a problem. Mark's indicator is working with an API that has been reverse engineered by Mark. So this is surely not the final solution. We are all yearningly waiting for BT to release the API....

Et voila: B6WGWJYQOOPHGSB3GOXPUUM6KK7LUP6S4 Since in 5 days none of the user id's I replicated with has provided any content, I consider my test now finished. I have the impression, the project is dead, since also the stream of the voleteam is not producing anything...