tuxpoldo

Members
 View Profile  See their activity

  • Posts

    730

  • Joined

  • Last visited

  • Days Won

    27

 Content Type 

Everything posted by tuxpoldo

  1. tuxpoldo
    Thank you very much! I've already planned to implement it in the next version of the server packages. Here the reference: Issue #96
  2. tuxpoldo
    Hi there, today I found an explanation for the strange "cannot connect" bug that several people encounters on startup. It seems that on some systems all processes are brutally killed on logout/shutdown leaving a lot of state files around. The following version should fix it (I hope). Please let me know. Here the changelog: btsync-user (1.14.3-1) unstable; urgency=low * New forked release 0.14.2 of btsyncindicator - Fixed TypeError on Debian Wheezy (Would close #btsyncindicator/45) * Fix handling of brutaly killed processes (Closes #60) and (Closes #94) -- Leo Moll <leo.moll@yeasoft.com> Wed, 12 Mar 2014 18:54:22 +0100
  3. tuxpoldo
    As I know, the webui and the predefined shared folders are mutually exclusive...
  4. tuxpoldo

    Done! The btsync-gui has reached feature completeness!

  5. tuxpoldo
    Hi Tommy! If during the installation you decided to create a default instance (it's the default), btsync will store all it's internal stuff in /var/lib/btsync In order to activate debugging, please issue the following commands from the console: sudo echo FFFF > /var/lib/btsync/debug.txtsudo service btsync restartYou will now find your debugging log in /var/lib/btsync/sync.log - please remember that the log file can become very huge, of you forget to disable logging when you do not need it any more... p.S.: what RomanZ wrote in the previous posting, is correct if you use the btsync executable as downloaded directly from BitTorrent Inc. by launching it manually. The btsync package, installs a full deployment scenario that controls where things are written and processes are managed.
  6. tuxpoldo
    Good morning, Ladies and Gentlemen! As promised yesterday, here comes the brand new release of btsync-gui. The changelog is impressive and I hope you will love it btsync-gui (0.7-1) unstable; urgency=low * Added support for suspend and resume (Closes #82) * Implemented shutdown handlers and provided more consistent agent startup behaviour (Closes #78) * Fixed security issue with agent configuration file (Closes #81) * Windows size is now persistent (Closes #77) * Added the possibility to make the web UI of the local agent accessible and to store default settings (Closes #83) * Implemented random per session credentials (Closes #67) * Fixed broken open SyncArchive and Folder when folder name contains spaces (Closes #85) * Added specific icons for paused and connecting state * Cyclic status updates are now dynamically adapted to the system and conncetion performance avoiding API flooding (Closes #88) * Finalized remote support (Closes #79) - Added connection information to status and window - Disabled browse button on remote connections - Disabled local file system checks on remote connections - Disabled folder open functions on remote connections * Added Web UI menu entry for advanced users (Closes #89) * Added forum link menu entry (Closes #90) * Added documentation menu entry (Closes #91) * Implemented management of predefined hosts (Closes #74) -- Leo Moll <leo.moll@yeasoft.com> Tue, 11 Mar 2014 13:48:01 +0100 Basically we are now ready to go in beta. As soon as I have updated the initial posting with a full documentation like for the legacy Desktop Packages and Server Packages, I will also deploy the GUI to Launchpad and the regular repository. p.s.: OK - the initial posting has been updated with a full documentation. The packages can now be downloaded also via the regular repository. p.s.s.: There was a missing package in the debian.yeasoft.net repository. It has now been fixed.
  7. tuxpoldo
    Done! We are feature complete! Tomorrow you will get a great new release! It was a huge todo list...
  8. tuxpoldo
    Great! You made my day! Let's get serious: take a look at a .SyncArchive (hidden) directory below your Desktop - If you are lucky, you will find there all your files...
  9. tuxpoldo
    Pure informational post: I'm also tracking the issue as Issue #86 - but I'm quite sure, it's a btsync issue....
  10. tuxpoldo
    I suppose that the refresh rate was to high for your configuration. While testing the GUI on remote systems, I had the same problem. Fixed (i hope): Issue #88 All of these are now solved by Issue #83 and Issue #89 Yes. You can install the btsync server package and then use btsync-gui only as client - see Issue #79
  11. tuxpoldo
    Hi Aslam! Thank you very very much for your valuable input! I appreciate a lot that you explained in detail what are the reasons for your vote. This is really helpful. The next version of btsync-gui, that I will release probably tomorrow, will provide a lot of enhancements that address many of the remarks you made. Today I reached code completeness for the beta stage (feature completeness) but you convinced me to add also the feature to invoke the web ui from the menu (See Issue #89). Good points. See Issue #90 and Issue #91 Thanks a lot!
  12. tuxpoldo
    There is no official 1.3 release yet.
  13. tuxpoldo
    Finally the update... btsync-common (1.2.91-2) unstable; urgency=low * Added support for AMD Geode CPU -- Leo Moll <leo.moll@yeasoft.com> Fri, 07 Mar 2014 16:27:01 +0100 btsync-common (1.2.91-1) unstable; urgency=low * New upstream release * Added support for btsync-gui when updating -- Leo Moll <leo.moll@yeasoft.com> Fri, 07 Mar 2014 13:37:33 +0100 1.2.91-2 is available only on debian.yeasoft.net since the Geode change is not relevant for Ubuntu (Ubuntu has no Kernel that runs on Geode machines). As usual people using the Launchpad PPA have to wait a few hours (perhaps you may take in consideration moving from the PPA to debian.yeasoft.net). One thing more: unfortunately Launchpad does not permit to update packages for outdated Ubuntu versions in the PPA. Because of this, there is no way to update the packages for Ubuntu Raring since the support has ceased. People using unsupported Ubuntu version must update to the debian.yeasoft.net repository if they want to stay up to date.
  14. tuxpoldo
    Finally the update... btsync-common (1.2.91-2) unstable; urgency=low * Added support for AMD Geode CPU -- Leo Moll <leo.moll@yeasoft.com> Fri, 07 Mar 2014 16:27:01 +0100 btsync-common (1.2.91-1) unstable; urgency=low * New upstream release * Added support for btsync-gui when updating -- Leo Moll <leo.moll@yeasoft.com> Fri, 07 Mar 2014 13:37:33 +0100 1.2.91-2 is available only on debian.yeasoft.net since the Geode change is not relevant for Ubuntu (Ubuntu has no Kernel that runs on Geode machines). As usual people using the Launchpad PPA have to wait a few hours (perhaps you may take in consideration moving from the PPA to debian.yeasoft.net). One thing more: unfortunately Launchpad does not permit to update packages for outdated Ubuntu versions in the PPA. Because of this, there is no way to update the packages for Ubuntu Raring since the support has ceased. People using unsupported Ubuntu version must update to the debian.yeasoft.net repository if they want to stay up to date.
  15. tuxpoldo
    Yes! Now we know that it works: Figure 7: btsync-gui on KDE with Debian Jessie
  16. tuxpoldo
    Don't forget: you can follow the work progress here. Only three open issues to the next milestone and for the time being we are feature complete. Maybe tomorrow?
  17. tuxpoldo
    Ladies and Gentlemen! Today we reached a milestone in democratic development. Through the Topic Poll you convinced me, that there are situations in which it may be useful to access the local BitTorrent Sync agent also from other computers. Also if this may have some security implications, the next version of btsync-gui will give you the freedom to override the Web UI address binding and to specify known credentials. See Issue #83 Et voilà: usage: btsync-gui [-h] [--log {CRITICAL,ERROR,WARNING,INFO,DEBUG}] [--host HOST] [--port PORT] [--username USERNAME] [--password PASSWORD] [--bindui BINDUI] [--savedefaults] [--cleardefaults]optional arguments: -h, --help show this help message and exit --log {CRITICAL,ERROR,WARNING,INFO,DEBUG} Sets the logging level. By default the logging level is WARNING --host HOST Hostname for the connection to BitTorrent Sync. If not specified, a local BitTorrent Sync agent will be launched. --port PORT Optional port number for the connection to BitTorrent Sync. If not specified, port 8888 is taken for a connection to a remote BitTorrent Sync agent or (8999 + uid) is taken when creating a locally lauched agent. --username USERNAME Optional user name for connecting to a remote BitTorrent Sync agent or username to use when creating a locally launched agent. --password PASSWORD Optional password for connecting to a remote BitTorrent Sync agent or username to use when creating a locally launched agent. --bindui BINDUI Optional bind address for the Web UI of a locally created BitTorrent Sync agent. By default the agent binds to 127.0.0.1. If you want the Web UI of the agent to be reachable by other computers, specify one of the available IP addresses of this computer or "all" to bind to all available adapters. --savedefaults If specified, the optionally supplied credentials, bind address and port will be stored as default in the application preferences and used when launching a local BitTorrent Sync agent. --cleardefaults If specified, all internally stored credentials, bind address and port information will be cleared from the application preferences.
  18. tuxpoldo
    Thank you! That's exactly the information I need. I think that I have a theory why this may happen: currently the GUI performs the refresh task quote often (once per second). I am sure, that I have to modify this and make the refresh a little bit more adaptive, since in case of a huge number of shared folders or a huge number of peers connected, the refresh task would flood the application and made the system unresponsive. Can you please tell me how many shared folders (an approximate estimation is enough for me) and connected peers are on your system? OK - I see you have read the thread. We are still discussing about the Web UI... Basically yes. But not if you are only using the GUI. The GUI is intended to be used exactly like the BitTorrent application on Mac OSX and Windows: an application that runs while the user is logged on. As I wrote as an answer to this posting, the current behaviour that BitTorrent Sync continues to run also after logout when btsync-user is installed, is a bug. If you want to run a headless BitTorrent Sync, the correct way is to handle it as a daemon (e.g. using a package like btsync - the server version). In the next version the GUI will support two separate modes: Standalone mode: when you start the GUI, also a corresponding BitTorrent Sync engine is started (that's the way it works now)Client mode: start the GUI and connect to a running BItTorrent Sync daemon by specifying host, port and credentials on the command line.In the next version I will add also some more logging in order to help solving such problems as you reported.
  19. tuxpoldo
    That's the meaning of the word "Alpha"... But we are all testers. Remember: BitTorrent Sync is still Beta.
  20. tuxpoldo
    Unfortunately not. What's about you? If it does not work, you can revert to btsync-user. The internal configuration files are saved in the same locations, so it is no problem to switch between them. Update: Yes! Now we know that it works with KDE: Figure 7: btsync-gui on KDE with Debian Jessie
  21. tuxpoldo
    You know? There are no stupid questions. There are only stupid answers First of all let's clarify one thing: both packages install the same BitTorrent Sync executable. Because of that, there are absolutely no differences between what BitTorrent Sync is able to do. The difference stays in the way, your machine handles BitTorrent Sync: If you install btsync-user (or the upcoming successor btsync-gui), you get an environment in which BitTorrent Sync is launched when you log in into your desktop as a process owned by you. When you logout, the process may be stopped (this is currently not happening with btsync-user, but it is a bug and may change in future...). This implies that the BitTorrent Sync process is able to read/write only files/directories on which YOU have write access. By default you work with a basic configuration file automatically created at each start. You can set advanced settings via the Web UI. There is also a possibility to use a custom configuration file in which you can specify everything you want. You can change settings in the Web UI, but at every restart these settings are overwritten by the settings you have specified into the configuration file.If you install btsync (the server package) one or more BitTorrent Sync processes are started on system startup. They run independently from the users that may log in to the desktop. Obviously they work also on systems with no desktop installed. For each of those BitTorrent Sync processes there is a configuration file located in /etc/btsync and each of this processes can run under different user credentials (that are coded into comments in their respective configuration files). Additionally there is the possibility to specify the UMASK for the process, if you want BitTorrent Sync to create/write files with a different UMASK as the standard one.Let's summarize: for you it makes sense to use btsync instead of btsync-user if:You want BitTorrent Sync to run totally independently from any user logged into the systemYou may want to have more than one instance running in future (this is the case, if you want to permanently synchronize the files of several users of the system). Yes. But first take a decision if the server package is really the right thing for you. If you say yes, I will explain here how you may migrate your system. Yes , it IS relevant... and: NO, this is NOT the wrong thread.
  22. tuxpoldo
    This is correct. I will think seriously about your idea. Perhaps it may be quite simple to implement it... I checked what happens on my Debian:My package installer created the desktop file in /etc/xdg/autostartThe "Startup Application Preferences" applet (gnome-session-properties) creates a copy in ~/.config/autostart and adds the following line to it:X-GNOME-Autostart-enabled=false I tried to write "Hidden=True" instead of X-GNOME-Autostart-enabled=false but it seems not have any effect. Perhaps I should try a combination of both in order to make sure it will work also on other desktops... Can you give me some more details (Distribution, Version)? I would like to enhance the compatibility list in the initial posting
  23. tuxpoldo
    +1 for IPv6!
  24. tuxpoldo
    Hi KuttKatrea! Thank you a lot for your thoughts. Let's discuss about all topics: OK - interesting use case. Nowadays this is not possible under Windows/MacOSX since both of them have NO web UI. Also the current Linux-Version (either with btsync-user or with btsync-gui) would not support this use case, since the Web UI is bound only to 127.0.0.1 for security reasons (that means: you can access it only from the local machine). But the use case may be interesting and could be solved in two ways: The manual way: manage the BitTorrent Sync engine on your own (bei either create your own configuration file and startup script or using the btsync server packages) and connect the GUI from the command line by supplying the connection parameters (this will be documented and supported in the next release).The comfortable way: provide a configuration option for the Web UI "public" (bound to all network interfaces) and configured with a known username and password. I have some ideas about how to implement it, but I will add a poll question to the topic to see how much users may be interested in such a feature. Unfortunately not. I know. The package already follows the XDG specification. On Gnome there is an additional control panel, that permits you to enable/disable autostart items. Obviously I can enable/disable autostart by creating/deleting the file in ~/.config/autostart/, but I would prefer to follow the method used by Gnome... BTW: Have you tested it? What is your impression?
  25. tuxpoldo

    Working hard on the next version of btsync-gui...