Search the Community
Showing results for tags 'umask'.
Found 3 results
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?
Hello QNAP Model: TS-809U Firmware version: 4.1.0 Bittorrent Sync verison: 1.3.109 Linux version: 3.4.6 (root@NasX86-13) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 Normally, by default, Bittorrent Sync runs on linux as the user: “root” and group: “administrators” and writes these owner:group permissions to syncronized files and folder that it creates. In the case of the QNAP NAS, Bittorrent Sync writes files and runs as the user “admin”. I have successfully managed to enforce all sub-folders and files in my sync folder to inherit the group “btsync” in the file permissions by using: chown admin:btsync /syncchmod g+s /syncThe problem is that Bittorrent Sync creates new files and folders with read-only permissions for the group “bysync” (i.e. wxr-xr-x / octal 0755). From researching I have found that the 2 ways to change this normally would be: 1) Add this line to the btsync.conf file and restart btsync: // DAEMON_UMASK=0022) Use the following command and when prompted enter "002" as the umask dpkg-reconfigure btsyncNeither of the 2 above methods resolve the issue. In the case of item 1, this setting seems to be ignored by btsync. With item 2, “dpkg-reconfigure” is not a command available on the version of linux used by the QNAP NAS. Thank you in advance for your help!
It seems like permissions in the destination are force-set to XX4 (where X = 6 or 7). My goal is to put "others" executable bit on directories, so it can be painlessly browsed by a web server, which is another user. Here are a few files: -rw-rw-r-- 1 motiejus motiejus 0 Apr 25 13:52 000 -rw-rw-r-- 1 motiejus motiejus 0 Apr 25 13:53 600 -rw-rw-r-- 1 motiejus motiejus 0 Apr 25 13:55 660 -rwxrwxr-- 1 motiejus motiejus 0 Apr 25 13:55 700 -rwxrwxr-- 1 motiejus motiejus 0 Apr 25 13:55 760 -rwxrwxr-- 1 motiejus motiejus 0 Apr 25 13:52 777 Name of the file corresponds to its permissions set by chmod in the original. Behavior of 660 and 760 is really strange. Why is the last executable bit not synchronized? Maybe it is possible to introduce some special 'umask' parameter to the config file to control this behavior? Thanks!