|CHFLAGS(1)||General Commands Manual||CHFLAGS(1)|
] flags file ...
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
-loto see the flags of existing files. 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.
archflag is for compatibility only, and currently has no effect. A file with the
nodumpflag set will by default only be backed up by dump(8) during full backups. The
-hoption of dump(8) can be used to alter this. 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
schgflags 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
nobefore a flag name causes the flag to be turned off. For example:
-Poptions are ignored unless the
-Roption is specified. In addition, these options override each other and the command's actions are determined by the last one specified.
chflagsutility exits 0 on success, and >0 if an error occurs. ls(1), chflags(2), stat(2), fts(3), securelevel(7), symlink(7), dump(8)
chflagscommand first appeared in 4.4BSD.
|August 25, 2018||OpenBSD-current|