GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
@@ -693,7 +693,7 @@ NOTE: The root account can still delete the file if it wants to.
==== 3.5.2 Special Permissions : SUID and SGID
When an executable is ran in Linux, it runs with the permissions of the user who started it. However, SUID and SGID change that to force the executable to run as the *owning user or group*. These permissions are represented as `s` in the *User* or *Group* field of `ls- l`.
When an executable is ran in Linux, it runs with the permissions of the user who started it. However, SUID and SGID changes that to force the executable to run as the *owning user or group*. These permissions are represented as `s` in the *User* or *Group* field of `ls- l`.
