Package Details: rslsync 3.0.3-1

Git Clone URL: https://aur.archlinux.org/rslsync.git (read-only, click to copy)
Package Base: rslsync
Description: Resilio Sync (ex:BitTorrent Sync) - automatically sync files via secure, distributed technology
Upstream URL: https://www.getsync.com
Licenses: custom:resilio
Submitter: widowild
Maintainer: widowild (fryfrog)
Last Packager: fryfrog
Votes: 362
Popularity: 0.84
First Submitted: 2016-09-25 13:20 (UTC)
Last Updated: 2025-03-24 00:23 (UTC)

Latest Comments

« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 35 36 37 .. 56 Next › Last »

tes5884 commented on 2014-06-12 15:51 (UTC)

Seems to be failing validity check. Maybe the hash needs to be updated.

ava1ar commented on 2014-05-23 04:42 (UTC)

@RubenKelevra I have no idea, you should better ask at http://forum.bittorrent.com/forum/107-bittorrent-sync/

RubenKelevra commented on 2014-05-22 18:41 (UTC)

Well is there any option to bind btsync to more than one interface or a specific one? Best regards Ruben

ava1ar commented on 2014-05-20 00:39 (UTC)

Updated to 1.3.105, @EasySly, thanks for the direct links!

EasySly commented on 2014-05-19 18:20 (UTC)

I propose to use static urls to btsync distributions: http://syncapp.bittorrent.com/${pkgver}/${pkgname}_${arch}-${pkgver}.tar.gz Please note that $arch is not the same as in pacman =( You can look at the updated PKGBUILD here http://pastebin.com/Bu0YNHXr

ava1ar commented on 2014-05-06 17:18 (UTC)

@emlun Thanks for the update. I read some docs and looks like %h is working for user services and do not work for system, so we are good here. After settings WantedBy=default.target mine starts fine too (I am using KDE4). Here is another question, coming to my mind: do we actually need btsync@.service now? Previously I was using it for running btsync as user, what is done via user service. For system-wide btsync execution, there is btsync.service. Is the any case left where we may need btsync@.service?

emlun commented on 2014-05-06 16:26 (UTC)

@ava1ar I followed the instructions in Systemd/User on the wiki, and my autostarts are working with WantedBy=default.target . I haven't tested to see whether they start on boot or wait until login, though. You might need to enable "lingering", which is also documented on the wiki. Also I'm not using a DM, I log in directly to the tty.

emlun commented on 2014-05-06 16:17 (UTC)

@ava1ar $ pacman -Q systemd; man systemd.unit | grep '%h' -A9 -B1 systemd 212-3 ├──────────┼─────────────────────────────────┼─────────────────────────────────┤ │"%h" │ User home directory │ This is the home directory of │ │ │ │ the configured user of the │ │ │ │ unit, or (if none is set) the │ │ │ │ user running the systemd user │ │ │ │ instance. Similar to "%U", this │ │ │ │ specifier is not available for │ │ │ │ units run by the systemd system │ │ │ │ instance, unless the configured │ │ │ │ user is the root user. │ ├──────────┼─────────────────────────────────┼─────────────────────────────────┤ Seems to work for me: ~ $ mkdir ~/tmp; cd ~/tmp; ls -la total 8 drwxr-xr-x 2 emlun emlun 4096 6 maj 18.14 . drwxr-x--- 103 emlun emlun 4096 6 maj 18.14 .. ~/tmp $ cat ~/.config/systemd/user/test.service [Service] Type=oneshot ExecStart=/usr/bin/touch %h/tmp/test ~/tmp $ systemctl --user start test.service ~/tmp $ ls -la total 8 drwxr-xr-x 2 emlun emlun 4096 6 maj 18.14 . drwxr-x--- 103 emlun emlun 4096 6 maj 18.14 .. -rw-r--r-- 1 emlun emlun 0 6 maj 18.14 test