• Posts

  • Joined

  • Last visited

Everything posted by acgamst

  1. cipherplain : Many thanks for the advice! It's easy to restrict the list of files to delete to those you say aren't critical, so I have done that. So far so good – after deleting the files the other day, there's been a small increase in the amount of space the files are taking, but 108M is a lot better than 21GB.
  2. Hearing no words of wisdom, I overcame my risk aversion and deleted every file in ~/Library/Application Support/BitTorrent Sync with a modification time more than 10 days ago. This freed up 21GB of space and, while BTSync is still writing new log files, removing the older files doesn't seem to have hurt anything. I am still not sure what's causing the problem – or even if it remains a problem, now – but my plan is to simply have cron run a clean-up script once every so often (every day or every week). Would still like to know what was causing the problem, so please post if you have any ideas.
  3. I am running BitTorrent Sync 2.0 on a MacBook Air, running Yosemite. I have been having trouble with my SSD filling up and I have tracked the problem down to, essentially, the size of the ~/Library/Application Support/BitTorrent Sync directory, which currently stands at 21GB (and growing). There are several different types of files in the directory -- settings.dat{.old}, history.dat{.old}, sync.dat{.old}, sync.log{.old}, lock,, *.db{-shm,-wal}, and .journal -- but the real problem seems to be with the *.journal.log files; there are hundreds of these, with 3 to 5 new ones every minute. What is causing this? Are these files safe to delete? Is there a setting which can be changed to either limit the rate at which these files are created or their total number?
  4. Many thanks for the help and explanation. As an update, the "use predefined hosts" seems to have solved the problem (for now?) and everything is working as expected. Port 3000 was open to and on both servers, but somehow this didn't help. I didn't do much analysis of the problem, unfortunately. Thanks again.
  5. I have read a bit more and I believe the solution to my problem may be "use predefined hosts" in the preferences associated with each of the individual folders. I'll try that ...
  6. Greetings, all! I am new to the forum, looked at the FAQ, and tried to search for an answer to my question, in case one already exists, but may have missed the answer anyway. My situation is this: I have BitTorrent Sync installed on several machines, sync-ing several (large) directories. At least 3 of these machines are Mac laptops which change location and IP addresses "very frequently" (on the order of a couple times a day, each). At least 2 of the machines are "servers", with fixed IP addresses. The problem is that when the laptops change location it often takes "forever" for them to find their peers. I set the folder_rescan_interval to 60, but that didn't seem to help -- I had hoped it would force the machines to announce themselves and sync more frequently, but it doesn't seem to have done "anything" (except, locally, perhaps). I am wondering: Is there a way to force BitTorrent Sync to find peers and sync? (Actually, how are peers identified and is there any way I can speed that process?) Alternatively, is there any way I can tell BT Sync "look here" (there's a peer at this IP address)? Or some way I can tell BT Sync: "this machine will 'always' be on-line at this address, go ahead and sync every M minutes"? I understand that this is a peer-to-peer architecture, but I am hopeful that someone has some advice for me. (Probably, some mechanism I haven't even thought about yet). Happy to answer questions if I have left out something important. In advance, many thanks. Hope all's well, Anthony