Package Details: rslsync 3.0.1-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: 361
Popularity: 0.23
First Submitted: 2016-09-25 13:20 (UTC)
Last Updated: 2024-10-12 04:43 (UTC)

Latest Comments

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 56 Next › Last »

ava1ar commented on 2014-08-30 02:09 (UTC)

@JibbsIsMe Did you follow the instructions displayed after package installation? Looks like not. If you want to user btsync user service, you should either configure it manually or use btsync-autoconfig package. Here are manual instructions, which are displayed after installation: User-specific BTSync configuration Copy /etc/btsync/btsync.conf to ~/.config/btsync/btsync.conf for the user you wish to configure btsync as: mkdir -p ~/.config/btsync cp /etc/btsync.conf ~/.config/btsync/btsync.conf Replace user-specific references with the appropriate information, including the following settings: - storage_path - pid_file - webui.listen - webui.login - webui.password Make sure folder you specified as storage_path and folder where pid_file will be located both exist in the filesystem, since btsync will not create it for you.

JibbsIsMe commented on 2014-08-30 02:04 (UTC)

After a fresh install, I had the error "Can't open pid file /sync.pid. Permission denied" when running "systemctl --user start btsync". "journalctl -xn" didn't provide enough info, so I ran "/usr/bin/btsync --config ~/.config/btsync/btsync.conf --nodaemon" and it showed me specifically where the .pid file was: "/usr/bin/.sync/sync.pid". So I fixed it by running "sudo chmod 777 /usr/bin/.sync/sync.pid" and now everything works.

ava1ar commented on 2014-08-26 20:06 (UTC)

Updated to 1.4.72. Please note: downgrade to 1.3 is not possible after installing Sync 1.4! If you want to downgrade - please uninstall Sync with removing all settings, then install 1.3 and configure all folders from scratch.

vaski commented on 2014-08-18 13:13 (UTC)

@emlun Thanks, this did the trick. @ava1ar Adding btsync to group users did not work, btsync would not start, complained about root folder

emlun commented on 2014-08-16 08:04 (UTC)

@vaski Or, if all else fails, you could modify the service by copying /usr/lib/systemd/system/btsync.service to /etc/systemd/system/btsync.service and change the User= setting to whatever user you need, and # systemctl daemon-reload. Service files in /etc override ones in /usr/lib.

ava1ar commented on 2014-08-16 04:10 (UTC)

@vaski Nothing to prevents you to add btsync to users group and give the group proper permissions for folders your are syncing in the /home/someusername. The only difference between 2 service files for btsync is that one is started by system instance of systemd and another by user instance. Seconds service works great for PC you are logging in, first for headless servers where no login normally performed at all.

vaski commented on 2014-08-15 23:34 (UTC)

@ava1ar Thanks, but I need to be able to sync folders in /home/someusername, and I ran into problems trying that using btsync.service

ava1ar commented on 2014-08-15 16:09 (UTC)

@vaski On headless server you can use btsync.service instead of user instance. It is running on separate user and does not depend on user login.

emlun commented on 2014-08-15 12:04 (UTC)

@vaski You could try enabling lingering [1]. Disclaimer: I'm not a systemd expert, most of what I know about how to get these things working comes from reading the wiki. :P [1]: https://wiki.archlinux.org/index.php/Systemd/User#Automatic_start-up_of_systemd_user_instances

vaski commented on 2014-08-15 12:00 (UTC)

@emlun, ahh you are right, when I install btsync on my desktop pc everything is working, but not on my headless server (where I got the failed d-bus connection). I don't login to the server, only access it with ssh so Systemd user instance does not start automatically, can I start it through ssh?