Search the Community

Showing results for tags 'rslsync'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. I was using resilio for a very long time, since first versions of btsync. now I have 2 PCs with win7 and ubuntu 16lts. I have noticed that all files sent from win7 PC have a lock icon on them, so I've used sudo chmod -R to change permissions for all the synced files. but every time I add smth to the sync folder using windows or edit an existing file, rslsync ubuntu user is writing it with locked permissions. there is also a similar thread here in the forum: so I guess I am not alone with this problem. did I set up something wrong?
  2. I'm on a Raspberry Pi 1B and this is what I get. $apt-get install resilio-sync .... Setting up resilio-sync (2.4.4-1) ... Job for resilio-sync.service failed. See 'systemctl status resilio-sync.service' and 'journalctl -xn' for details. invoke-rc.d: initscript resilio-sync, action "start" failed. dpkg: error processing package resilio-sync (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: resilio-sync E: Sub-process /usr/bin/dpkg returned an error code (1) :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: $sudo systemctl status resilio-sync.service ‚óŹ resilio-sync.service - Resilio Sync service Loaded: loaded (/lib/systemd/system/resilio-sync.service; enabled) Active: failed (Result: start-limit) since Fri 2016-12-16 00:47:27 PST; 5min ago Docs: http://help.getsync.com/ Dec 16 00:47:27 RPi1B systemd[1]: Unit resilio-sync.service entered failed state. Dec 16 00:47:27 RPi1B systemd[1]: resilio-sync.service holdoff time over, scheduling restart. Dec 16 00:47:27 RPi1B systemd[1]: Stopping Resilio Sync service... Dec 16 00:47:27 RPi1B systemd[1]: Starting Resilio Sync service... Dec 16 00:47:27 RPi1B systemd[1]: resilio-sync.service start request repeated too quickly, refusing to start. Dec 16 00:47:27 RPi1B systemd[1]: Failed to start Resilio Sync service. Dec 16 00:47:28 RPi1B systemd[1]: Unit resilio-sync.service entered failed state. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: $ sudo journalctl -xn -- Logs begin at Thu 2016-12-15 19:47:48 PST, end at Fri 2016-12-16 00:51:18 PST. -- Dec 16 00:47:27 RPi1B systemd[1]: Failed to start Resilio Sync service. -- Subject: Unit resilio-sync.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit resilio-sync.service has failed. -- -- The result is failed. Dec 16 00:47:28 RPi1B systemd[1]: Unit resilio-sync.service entered failed state. Dec 16 00:47:31 RPi1B sudo[4538]: pi : TTY=pts/0 ; PWD=/etc/init.d ; USER=root ; COMMAND=/usr/bin/dpkg --configure resilio-sync Dec 16 00:47:31 RPi1B sudo[4538]: pam_unix(sudo:session): session opened for user root by pi(uid=0) Dec 16 00:47:32 RPi1B systemd[1]: Reloading. Dec 16 00:47:33 RPi1B systemd[1]: Reloading. Dec 16 00:47:34 RPi1B sudo[4538]: pam_unix(sudo:session): session closed for user root Dec 16 00:47:34 RPi1B systemd[1]: Failed to send queued message: Transport endpoint is not connected Dec 16 00:51:18 RPi1B sudo[4614]: pi : TTY=pts/0 ; PWD=/etc/init.d ; USER=root ; COMMAND=/bin/journalctl -xn Dec 16 00:51:18 RPi1B sudo[4614]: pam_unix(sudo:session): session opened for user root by pi(uid=0) :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: $sudo dpkg --configure resilio-sync Setting up resilio-sync (2.4.4-1) ... Job for resilio-sync.service failed. See 'systemctl status resilio-sync.service' and 'journalctl -xn' for details. invoke-rc.d: initscript resilio-sync, action "start" failed. dpkg: error processing package resilio-sync (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: resilio-sync :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: I also get this error: $systemctl --user enable resilio-sync Failed to get D-Bus connection: No such file or directory Any idea what's going wrong?
  3. I have four directories on my linux system that I want to sync. For local security and management purposes, each folder (and all its contents) should have a different group owner and umask 0027. So, I thought I would initiate four parallel installs of rslsync. Each would be configured with just one of the folders shared. And rslsync would be launched with the desired group and umask settings four times. I've run into trouble because it seems the configuration for the second "instance" is clobbering the first. (which was initially working fine) I don't understand how to use these options appropriately. --config <path> Use a configuration file --storage <path> Storage path for identity and license Right now, without either specified, the second instance has interfered with the first. There is the .sync folder created in the shared folder. But there is also the .sync folder created... I guess under the working directory of the rslsync executable. Can anyone explain the stuff in the later folder, and how I might keep it all separated?