thx

I just learnd, that systemd user instances indeed have no multi-user as target! See man 7 systemd.special #SPECIAL USER UNITS so, for user instances default would be the correct target I suppose - combined with lingering

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 btsync Still, btsync did not start at boot. Remedy was to change the target for the btsync target from multi-user to default in the [Install] section in /usr/lib/systemd/user/btsync.service > /usr/lib/systemd/user/btsync.service # WantedBy=multi-user.target #original target WantedBy=default.target # working target After disabling and enabling again btsync with systemctl for my user for resetting the link to match the target, i.e., $HOME/.config/systemd/user/default.target.wants/btsync.service btysnc starts finally at boot under my user. I suspect, that maybe the network may be was an obstacle for multi-user as target, since not necessarily I have a network at start (is multi-user coupled with network-online??) Maybe somebody has an idea, what possible drawback could be with default as target? From what I see, it can change at some point (current graphical). Maybe graphical is not the optimal target. Anyway, I had thought that graphical downstream of multi-user, so I wonder why it is working Cheers, Thomas

Hi, I have created a Sync v2.3.8 jail on my FreeNAS v9.10 box. Problem is, that the WebUI is not reachable. I can ping the jail's IP(v4) (locally fix, outside of my DHCP range), but no one is listening on port 8888. A btsync process is running in the jail listening on 49692/udp (if I get the BSD netstat -4 -l right...) but no one on 8888. With sockstats -l -4 I see the btsync PID listening on 49692 and 12349 on the external IP and on 8888 only for 127.0.0.1. I guess, I have to configure sync to listen on the external interface in addition, or? Question would be where/how? I found /.sync/settings.dat in the jails root, however vi throws an error "Conversion error on line 1 / Error: unable to retrieve line 1", whereas I can cat/less the file - including some broken(??) characters at the end of the first line at 'peer_id20:' If the plugin/jail is corrupted, I would wonder since I had assumed that they are checksumed in the FreeNAS repo? Cheers and thanks for ideas, Thomas

Hi Helen, unfortunately, I have moved on my desktop in the meantime from the containerized client to run it directly within my user's context, i.e., > systemctl --user {start,enable} btsync I have to see, if I have kept the container logs in a snapshot Anyway, running sync directly in the user context has no problems syncing. So, I suspect with the container either network issues (which would be strange, since both setups have been using the same ports on the host) or file system permission/ACLs related problems (would also be strange, because the user directory was readable/writable in the containter context (root...) with .sync in the folder successfully created. Does Sync use inotify for tracking file system changes on Linux? If so, my best guess would be, that inotifies are not passed through to a container (but should be the same kernel, so...?). But I am not really an expert on containers or file systems Cheers, Thomas

Hi all, I have troubles automatically syncing directories in my user context with having the Sync instance encapsulated in a Docker container (having a Pro licence) Using the Sync-Dockerfile [1] [2] (afais Ubuntu 15.04), I have setup an instance on a Ubuntu based server and anothe rinstance on my Fedora 23 desktop. the server's data directory points to a btrfs subvolume, i.e., DATA_FOLDER="/data/sync/" > docker run -d --name Sync -p 127.0.0.1:$WEBUI_PORT:8888 -p 55555 -v $DATA_FOLDER:/mnt/sync --restart on-failure bittorrent/sync on the desktop I mount additionally my user's home to be able to sync selectively directories, i.e., into the containers /mnt/mounted_folders path (afais the target path for additional directories in the container's default config) > docker run -d --name Sync -p 127.0.0.1:$WEBUI_PORT:8888 -p 55555 -v $DATA_FOLDER:/mnt/sync -v /home/MYUSER:/mnt/mounted_folders/MYUSER --restart on-failure bittorrent/sync When I add on my desktop a directory from my user's home path, it appears in principle after some time in the server's WebUI and the base directory created in server:/data/sync/folder/... However, no files are being synced and the directory on the server stays empty. On the desktop, a .sync firectory is created being owned by root as the docker daemon's owner. I have already tried to decrease the scan frequency to 300s just in case the file system notifies are not being passed through to the container(??) - but without success and the content of the user folder is not synced. Maybe somebody has an idea for me, how to get the user folder synced? Cheers and thanks, Thomas