Group member cannot write even with write permission
The logged in user is a member of a group that has a write permission on a folder. But when this user is trying to write something, “permission is denied”.
permissions
Why is rm allowed to delete a file under ownership of a different user?
From the post Why can rm remove read-only files? I understand that rm just needs write permission on directory to remove the file. But I find it hard to digest the behaviour where we can easily delete a file who owner and group different.
How to set permissions in /sys/ permanent?
I’m starting X as a user and need to set my keyboard brightness in /sys/class/leds/asus::kbd_backlight/brightness. The /sys/ directory gets recreated after reboot, so the permissions will reset too. How do I set it up so I don’t need to make the file writable by all users after every boot?
Permission denied to change gid(group) of a file I own
It appears I still miss some things about the way permissions work. I am on a debian 7 system btw.
just now I have this file of which I downloaded and it belongs to myuser:myuser, that is both user and group are set to me. It also resides in my $HOME directory since that is where I downloaded it to.
What’s the difference between “s” and “S” in ls -la?
When I ls -la, it prints many attributes. Something like this:
Is there any way to prevent deletion of certain files from user owned directory?
Let’s say user has Directory1 and it contains File1 File2 CantBeDeletedFile
How to make so the user would never be allowed to delete the CantBeDeletedFile?
Hard link permissions behavior different between CentOS 6 and CentOS 7
I’m getting a permissions error in CentOS 7 when I try to create a hard link. With the same permissions set in CentOS 6 I do not get the error. The issue centers on group permissions. I’m not sure which OS version is right and which is wrong.
What does a dot after the file permission bits mean?
I performed an ls -la on directory on my CentOS 6.4 server here and the permissions for a given file came out as:
Configure SELinux to allow daemons to use files in non-default locations
I have a daemon (apache/samba/vsftpd/…) running on SELinux enabled system and I need to allow it to use files in a non-default location. The standard file permissions are configured to allow access.
Move file to another user’s home directory (without sudo)?
I have a couple of files that I want to move to another’s user home directory. I don’t have permissions to write to that user’s home directory, but I know his password.