Arch Linux User Repository

@avat1ar When transfering, the log is reporting a line for each segment of a file that is completed: Aug 06 17:45:51 blue btsync[24004]: file X: Piece 182 complete Aug 06 17:45:52 blue btsync[24004]: file X: Piece 183 complete Aug 06 17:45:52 blue btsync[24004]: file X: Piece 184 complete Aug 06 17:45:52 blue btsync[24004]: file X: Piece 185 complete Then, once it completes syncing the files I am getting these strange "Blocked downloading" messages related to a couple files and their respective lock files Aug 07 09:26:44 blue btsync[27157]: Blocked downloading file X.xlsx due Connection closed Aug 07 09:26:44 blue btsync[27157]: Blocked downloading file ~$X.xlsx due Connection closed Aug 07 09:26:44 blue btsync[27157]: Blocked downloading file Y.xlsx due Connection closed Aug 07 09:26:44 blue btsync[27157]: Blocked downloading file ~$Y.xlsx due Connection closed Thanks again for any help on this. @emiun, I will take a look and see if I have a user defined service, I am using the system wide one, I am the only user of this machine.

@dam5h, I don't know of a way to configure btsync, so you're probably stuck with redirecting its output somewhere else. You could try overriding /usr/lib/systemd/user/btsync.service with one in ~/.config/systemd/user (or /etc) and monkey around with that. If all else fails, you could wrap the btsync call in a shell script that does some filtering on stdout (`btsync | grep foo` or the like).

@dam5h What type of entries you have in the log? Do they appears only when you are transferring something or all the time btsync is running? Can you dump somewhere part of your log to take a look?

@avat1ar, have you been able to look into the logging issue lately? I a getting huge journalctl files when I leave btsync running. They grow so fast I can't leave it running for more than a few hours before deleteing some of the journal. Thanks!

Yep, missprint :)

@ava1ar I suppose the @ in btsync_user@.service is a typo? :) In other words, this use is no longer supported: root@nsa # systemctl start btsync@alice Use this instead: alice@nsa $ systemctl -- user start

Updated to 1.3.109. btsync@.service removed, so please use btsync.service and btsync_user@service.

Version 1.3.109 released http://syncapp.bittorrent.com/1.3.109/

@jancici Consider using the user service instead, the btsync@user service (which is a system service) is deprecated. $ systemctl --user start btsync $ systemctl --user enable btsync # Will start on first login, see the wiki [1] for how to start on boot [1]: https://wiki.archlinux.org/index.php/Systemd/User#Automatic_start-up_of_systemd_user_instances