|CHFLAGS(1)||General Commands Manual||CHFLAGS(1)|
chflagsutility modifies the file flags of the listed files as specified by the flags operand. The flags of a file dictate special restrictions beyond those enforced by its mode/permissions. Only the superuser can change the user flags on block and character devices.
You can use
ls -lo to see the flags of
The options are as follows:
-Roption is also specified, symbolic links on the command line are followed. Symbolic links encountered in the tree traversal are not followed.
-Roptions are mutually exclusive.
-Roption is also specified, all symbolic links are followed.
-Roption is also specified, no symbolic links are followed.
Flags are a comma separated list of keywords. The following keywords are currently defined:
arch set the archived flag (superuser only) nodump set the nodump flag (owner or superuser only) sappnd set the system append-only flag (superuser only) schg set the system immutable flag (superuser only) uappnd set the user append-only flag (owner or superuser only) uchg set the user immutable flag (owner or superuser only)
The “arch” flag is for compatibility only, and currently has no effect.
An immutable file may not be changed, moved, or deleted. An append-only file is immutable except that data may be appended to it.
The superuser-settable “sappnd” and “schg” flags can be set at any time, but may only be cleared when the system is running at security level 0 or -1 (insecure or permanently insecure mode, respectively). For more information on setting the system security level, see securelevel(7).
Putting the letters “no” before a flag name causes the flag to be turned off. For example:
nouchg the immutable bit should be cleared
-P options are ignored unless the
-R option is specified. In addition, these options
override each other and the command's actions are determined by the last one
chflagsutility exits 0 on success, and >0 if an error occurs.
chflagscommand first appeared in 4.4BSD.
|December 31, 2015||OpenBSD-6.1|