New Members
  • Posts

  • Joined

  • Last visited

Acumen's Achievements

New User

New User (1/3)

  1. I just upgraded my DS414 to DSM 6.1-15047 and after a relatively long time of 99% CPU, all seems to be running fine.
  2. Hi All, I am curious if anyone upgraded his Synology to DSM 6.1-15047 already, what version of Resilio you are running and if it still functions. I am running a DS414+ with Bittorent Sync v2.3.8.1
  3. Well you can just modify the URL, for example: becomes btw, on my 414, BTSync is working with version 2.2.7
  4. Well, that is not a pleasant message... Can anyone of BTSync confirm the IF part of this message?
  5. Besides the increasing resources, here is possible solution to your rootfs filling:
  6. Okay, now I get it... Since I use the script below to run btsync as a service on my RasPi, I did not relate the 'current directory' thing. So, when I call the script manually, BTSync creates the .sync directory within the current Working Directory... So, at boot time that is the Root, but when manually entered '/etc/init.d/btsync start' you have to be careful where to enter the command. #!/bin/sh # /etc/init.d/btsync # # Carry out specific functions when asked to by the system case "$1" in start) /<btsyncpath>/btsync ;; stop) killall btsync ;; *) echo "Usage: /etc/init.d/btsync {start|stop}" exit 1 ;; esac exit 0
  7. @RomanZ So I was right, I missed something in the release notes. Did not relate 'in the current directory' to the root. @cpellerano I made a Symbolic link from the new .sync location to the folder where my original folder was located. In my case, after stopping btsync: - standing in root, remove the /.sync directory - creating a symlink: sudo ln -s /...<target>.../.sync/ .sync
  8. I run a Rasbian (Raspi + Debian) and update BTSync by stopping btsync, replacing the btsync file for the new one and restarting it again. I noticed my identity was gone. A quick check learned that there was a .sync directory in the root. I solved the issue with a symbolic link to the .sync location of the previous version and things are fine now, but I am wondering if I missed something in the release notes, is it an undocumented change or am I doing something wrong?
  9. Hi, I noticed the trash time to live setting, believing that the current '.sync/Archive' directory is mentioned by trash. In my sync construction I generate multiple copies per day of large files (like outlook PST files). It would be great if the feature could be added to store just one (as in the previous version of the current/most recent stored) version instead of/next to a time to live. Cheers!