3
The root user of Linux doesn't have permission to read/write a regular file, unless all users have permission to read/write this file, like below:
drwxrwsrwx ....... file_name
However the owner of the file can still read/write this file.
AND:
0) not the problem of execution, just read/write
1) not the problem of device because regular user can read/write it.
2) the result of command id
:
uid=0(root) gid=0(root) groups=0(root)
so I don't think it's the problem of group.
So what other problems could be?
In case anyone else is being stupid and winds up here, I ran into a similar issue because I was trying to delete a bunch of files in a Samba share from a different machine. I wasn't allowed to delete them, or to change the permissions, as root because the root I was using wasn't the root on the machine where the files were actually stored. – Soren Bjornstad – 2016-08-20T20:30:55.920
1
You may get a better response asking your question in http://unix.stackexchange.com/
– Johnsyweb – 2011-03-23T06:51:56.6631Is this filesystem on an NFS export? – Kirby Todd – 2011-03-23T06:57:45.453
yes, I guess it maybe the problem of NFS. Thx a lot – None – 2011-03-23T07:38:55.480
If the output is really is
drwxrwsrwx ....... file_name
and the seventh letter (s
instead of-
orx
) isn't a typo, then thes
means aSUID
Bit is set -> *S(et) U(ser) ID on execution. This means that other users can execute `file_name*with the *same permissions as the user who owns*
file_name. But as
rootis above all users, it should be able to read the file. Guessing that you are on a GNU/Linux system: What message do you get when trying to read this file as
rootuser? Also: Please describe how you do log in as
root` – erch – 2013-12-07T20:08:24.930