Skip to content

# minor changes to special authority #1244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 6, 2023
Merged

# minor changes to special authority #1244

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/books/admin_guide/14-special-authority.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ Shell > setfacl <option> <FILE_NAME>
| -k | remove the default ACL |
| -R | recurse into subdirectories |

Use the teacher's teaching example mentioned at the beginning of the article to illustrate the use of ACL.
Use the teacher's example mentioned at the beginning of the article to illustrate the use of ACL.

```bash
# The teacher is the root user
Expand Down Expand Up @@ -449,7 +449,7 @@ The role of "Sticky BIT":

SBIT is represented by the number **1**.

Can the file/direcyory have **7755** permission?
Can the file or directory have **7755** permission?
No, they are aimed at different objects. SUID is for executable binary files; SGID is used for executable binaries and directories; SBIT is only for directories. That is, you need to set these special permissions according to different objects.

The directory **/tmp** has SBIT permission. The following is an example:
Expand Down