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
Copy file name to clipboardExpand all lines: docs/books/admin_guide/14-special-authority.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -261,7 +261,7 @@ Shell > ls -l /project
261
261
```
262
262
263
263
Now there is a question: if I create a new file in this directory, does it have ACL permission?
264
-
The answer is no, because the newly created file is after the command `setfacl-m u:tom:rx -R /project` is executed.
264
+
The answer is no, because the newly created file is after the command `setfacl-m u:tom:rx -R /project` is executed.
265
265
266
266
```bash
267
267
Shell > touch /project/file3
@@ -402,7 +402,7 @@ Shell > chmod g-s FILE_NAME
402
402
403
403
!!! warning
404
404
405
-
When the owner group of an executable binary file/program does not have **x**, the use of capital **S** means that the filecannot use GUID permissions.
405
+
When the owner group of an executable binary file/program does not have **x**, use uppercase **S** to indicate that the file's SGID permissions cannot be used correctly.
0 commit comments