Search the Community

Showing results for tags 'user'.

  • 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. Hi, I am using the Official Docker container and have multiple mounted_folders setup, for the sake of debugging i will limit that to one. The container is launched via docker-compose, the volume is mounted at launch /start and i can access it with the UI and write data in there (read sync a folder), but all files have root:root ownership. Any idea how to get the ownership of the file within this folder to be the same as the parent mounted folder ? --- According to Docker discussions, the volume will have ownership of the user in the container (which seems to be
  2. I'm pulling my hair out here. I updated to 2.3.3 to use the new encrypted folders. The set up is quite a bit different, since it doesn't appear to have the dpkg option where you can select the user it runs under. I can get it to launch as user btsync, but cannot for the life of me get the btsync user to access the second hdd on my computer. I have added btsync to my user group that has access, added read/write privileges, everything. It won't even drill past /media/USER/ when trying to add a folder from the web gui, and manually entering a directory says it doesn'
  3. Hi, I just solved an issue I had - just wnated to document it in case it's of some use? I had trouble to automatically start Sync under my user on my Fedora 23 laptop at boot. Although I had enabled btsync as systemd service under my user, it did not start up even after I entered my graphical session. In addition I enabled lingering for my user, i.e., to start a user manager for my user at boot and after logout - so that services under my user will survive me logging out... > sudo loginctl enable-linger $USER > systemctl --user enable btsync > systemctl --user start btsy