aslamK

Members
  • Content Count

    22
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by aslamK

  1. I join those who are confused about whether btsync-gui-gtk is expected to work with BitTorrent Sync 2.0. I use the following repo: deb http://ppa.launchpad.net/tuxpoldo/btsync/ubuntu trusty mainThis contains v. 1.4 (btsync-common) as well as v. 2.0 (btsync-core & btsync). I am under the impression that btsync-gui is not yet ready for 2.0 so I'm still running v. 1.4. Would you confirm the current status of btsync-gui wrt BitTorrent Sync 1.4/2.0?
  2. Thanks, @tuxpoldo. Just read the initial post. There seems to be enough flexibility in btsync-gui to allow me to do what I want. So far, I'm using btsync only across a LAN and can set up any machine on the LAN to access the web UI of every btsync server on the LAN. Based on what I read, this should be possible with btsync-gui. I'll test this within the next couple of days. I don't have btsync-user & btsync-gui installed at the same time. I went back and forth by unstalling one and installing the other.
  3. btsync-gui v. 0.7-5 A couple of things I noticed, not sure if they are related: - This is the command associated w/ the btsync process: /usr/lib/btsync-common/btsync-core --config /home/myname/.config/btsync/btsync-agent.conf ...but there isn't a btsync-agent.conf in that location -- what is this file supposed to contain and where does that info come from when the file doesn't exist? - My credentials for the web UI, which work w/ btsync-user, don't work when I'm running btsync-gui.
  4. I voted No (would like to keep btsync-users). If btsync-gui incorporated the UI/features of btsyn-users, I would of course be happy with a replacement. This is what I like about btsync-users: - List of all shares at first down-click, and share specific action upon click-release via submenu. - Easy access to the BitTorrent Sync web console (Linux). - Easy access to sync pause/resume/quit and debug log toggle. The config UI in btsync-gui is great, particularly because one can glance at all available options (preferably with both current and default values visible) without having to look at th
  5. This works, thanks. It would help to have a doc that lists the complete .SyncIgnore syntax from the horse's mouth, as it were. This is particularly true for any syntax that varies from OS conventions like what @stanha points out.
  6. Thanks, RomanZ. Is there a way to have btsync ignore the files at the top-level as I described?
  7. That contradicts the documentation which says, "Note that .SyncIgnore is applied only to the folder where it is contained..."
  8. I _don't_ want to sync *.avi, *.mp4 files in the top-level/parent folder. I _do_ want to sync *.avi, *.mp4 files in the subfolders. Only the top-level/parent folder has the .SyncIgnore file, so why are the files in the subfolders not getting synched?
  9. Added a folder with video files to be synched across a LAN only. I wanted to sync files in subfolders and exclude any in the parent folder. The user guide has the following note... ...so I figured that adding the following lines would accomplish what I wanted:*.mp4*.aviI put a .SyncIgnore file with these lines in the directory to be synched on both machines before adding the folder in BTSync. Upon adding the folders I find that everything in the subfolders gets synched except the media files with the above extensions. The web console (Linux) reflects this, showing about 60kB in the folder in
  10. The .SyncIgnore file in the folder to be synced needs to be identical on both machines -- see the "Do I have an option to ignore some files during sync?" section in the Unofficial FAQ (http://forum.bittorrent.com/topic/16410-bittorrent-sync-faq/). Since there isn't a "SyncInclude" feature, there isn't an easy way to specify a subset of the subfolders to sync between the two machines, AFAICT. If the number of subfolders to sync is small compared to the total number of subfolders, it may be easier to sync each separately.
  11. Yes, the absence of a central entity that hosts the content and metadata makes it very unlike Twitter. However, a user/folder whose key is published (with or without the users' knowledge/consent) on a public site mimics Twitter in that all nodes synching with it are visible to each other. As I said earlier, this may be acceptable as long as the participants are aware of it.
  12. It's interesting how Vole shares appear on the BTSync UI -- this is the first time I've had an opportunity to share folders w/ multiple people. Looks like any node synching with a share folder whose key is publicized appears on the UI of all other nodes that synch using that key. Each Vole folder is showing me multiple nodes that I don't recognize, presumably these are other nodes that are synching w/ that same ones as I am. This info is not just extraneous to me, I am also seeing nodes whose owners most likely don't expect to have their nodes revealed to me -- I didn't expect that my node wou
  13. I had forgotten about the --nodaemon option, so thanks Unfortunately, launching btsync w/ the --nodaemon option appended to the command did not cause the process to exit when the session terminated -- if it weren't already running it would be launched through a script that has a launcher in ~/.config/autostart/ as you suggested.
  14. OS: Ubuntu 13.04 I noticed that the BTSync process survives across sessions, even though it runs as the login user (not root). If this is expected/intended behaviour, can you explain why?
  15. Just set this up and joined. Neat!
  16. I did the following to get LAN-only sync working without using external servers: Edit the conf file on each machine to set the listening port to a constant value (the default is 0, which results in random port nos.) Open the ports used above on the respective machines to allow ALL INCOMING. If synching does not happen after the above (it didn't for me), enable "Use predefined host" for the folders on one of the machines and add the other machine's ip:port. I don't think #3 should be necessary, but I can't get LAN-only sync to happen without it if I don't want to use external servers/relays.
  17. "Multicast Streams" was disabled on the router. I enabled it and rebooted the router. The behaviour remains the same: Folder does not appear as synching on the web UI until I check 'Use predefined host' and add the ip:port on one of the two machines.
  18. Upon looking at the sample config file more carefully, I learned that "listening_port" can be made constant :$ ... (Being able to specify a range of numbers here, would give a degree of randomness to the port no.) This is fine when if the synching is only within a LAN. However, if 'Search LAN' is checked and the listening ports are open, why do I also need to enable 'Use predefined hosts' and provide the ip:port?
  19. After btsync is freshly launched, it's apparently not enough to open up the ports as describe in my previous post. The synching doesn't start until "Use predefined host" is checked, and the other machine's ip:port is added, for each folder; however, this only needs to happen on one of the machines. Once the sync gets going, disabling "Use predefined host" and removing the ip:port does not seem to affect the sync, until btsync is stopped and started again. This, in addition to having to manually open new ports (and close old ones) after launch, is obviously quite cumbersome.
  20. OK... So I set the ports on the respective machies to Allow all incoming TCP/UDP -- got the port nos. from Preferences on the web GUI.The GUI now shows that the sync is happening. The ports seem to get set randomly when the BTSync process starts. Can I configure the port to be from a range of numbers so that I can allow incoming on those ports without having to do so manually every time I launch BTSync?
  21. Re: v. 1.1.48 on Linux Mint 15 & Ubuntu 13.04 I find that folders do not connect with their sync counterparts on a LAN if Relay and Tracker servers are not enabled in the following situations: when the folders are first added, and after BTSync is started. The folders do continue to sync after disabling Relay and Tracker servers after the initial connect. Is this expected/intended behavior?