You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The install script preserves the permissions that the file has in the repository. client/usr/bin/rs-backup-suite has permissions 755 in the repository. If it has something else on your system, then either something's wrong with your umask or you changed permissions.
I use the default umask on both the server (Debian Jessie) and clients (Debian Stretch and Ubuntu 16.04), with nothing added/changed in the users' environment variables:
$ git clone https://github.com/phoerious/rs-backup-suite.git
$ ls -l rs-backup-suite/
total 56
drwxrwx---+ 4 USER users 4096 May 16 17:33 client
-rwxrwx---+ 1 USER users 9871 May 16 17:33 install.sh
-rw-rw----+ 1 USER users 17806 May 16 17:33 README.md
drwxrwx---+ 5 USER users 4096 May 16 17:33 server
lrwxrwxrwx 1 USER users 10 May 16 17:33 uninstall.sh -> install.sh
OK. What I totally forgot is that this system is a NAS (OpenMediaVault) with ACL rules that freakin superseed the standard CLI/system ones.
I'll start it all over again and come back here report how it goes. Hopefully soon, this time.
Before I go further, please what is the reason for the default root only permissions on every rs-backup executables && conf files?
Default permissions on the client:
Same occurs once I can access the server after chmoding the above to 755:
Default permissions on the server:
The text was updated successfully, but these errors were encountered: