chflags(1) [netbsd man page]

CHFLAGS(1)						    BSD General Commands Manual 						CHFLAGS(1)

NAME

     chflags -- change file flags

SYNOPSIS

     chflags [-R [-H | -L | -P]] [-h] flags file ...

DESCRIPTION

     The chflags utility modifies the file flags of the listed files as specified by the flags operand.

     The options are as follows:

     -H      If the -R option is specified, symbolic links on the command line are followed.  (Symbolic links encountered in the tree traversal
	     are not followed.)

     -L      If the -R option is specified, all symbolic links are followed.

     -P      If the -R option is specified, no symbolic links are followed.

     -R      Change the file flags for the file hierarchies rooted in the files instead of just the files themselves.

     -h      If the file or a file encountered during directory traversal is a symbolic link, the file flags of the link itself is changed.

     Flags are a comma separated list of keywords.  The following keywords are currently defined:

	   Keyword	 Flag		       Permission
	   arch 	 archived	       super-user only
	   opaque	 opaque 	       owner or super-user
	   nodump	 nodump 	       owner or super-user
	   sappnd	 system append-only    super-user only
	   schg 	 system immutable      super-user only
	   uappnd	 user append-only      owner or super-user
	   uchg 	 user immutable        owner or super-user

     Putting the letters ``no'' before an option causes the flag to be turned off.  For example:

	   nouchg  the immutable bit should be cleared

     The -H, -L and -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 specified.

     The -o option of ls(1) is used to display the flags.

     The chflags utility exits 0 on success, and >0 if an error occurs.

     The kernel does not allow the flags on block and character devices to be changed except by the super-user.

SEE ALSO

     ls(1), chflags(2), lchflags(2), stat(2), fts(3), symlink(7), dump(8), init(8)

BSD
								   May 14, 2010 							       BSD

CHFLAGS(2)						      BSD System Calls Manual							CHFLAGS(2)

NAME

     chflags, lchflags, fchflags -- set file flags

LIBRARY

     Standard C Library (libc, -lc)

SYNOPSIS

     #include <sys/stat.h>
     #include <unistd.h>

     int
     chflags(const char *path, u_long flags);

     int
     lchflags(const char *path, u_long flags);

     int
     fchflags(int fd, u_long flags);

DESCRIPTION

     The file whose name is given by path or referenced by the descriptor fd has its flags changed to flags.  For lchflags(), symbolic links are
     not traversed and thus their modes may be changed with this call.

     The flags specified are formed by or'ing the following values:

	   UF_NODUMP	 Do not dump the file.
	   UF_IMMUTABLE  The file may not be changed.
	   UF_APPEND	 The file may only be appended to.
	   UF_OPAQUE	 The file (if a directory) is opaque for union mounts.
	   SF_ARCHIVED	 The file is archived.
	   SF_IMMUTABLE  The file may not be changed.
	   SF_APPEND	 The file may only be appended to.

     The UF_NODUMP, UF_IMMUTABLE, UF_APPEND, and UF_OPAQUE flags may be set or unset by either the owner of a file or the super-user, except on
     block and character devices, where only the super-user may set or unset them.

     The SF_ARCHIVED, SF_IMMUTABLE, and SF_APPEND flags may only be set or unset by the super-user.  Attempts by the non-super-user to set the
     super-user only flags are silently ignored.  These flags may be set at any time, but normally may only be unset when the system is in single-
     user mode.  (See init(8) for details.)

RETURN VALUES

     Upon successful completion, a value of 0 is returned.  Otherwise, -1 is returned and the global variable errno is set to indicate the error.

ERRORS

     chflags() will fail if:

     [ENOTDIR]		A component of the path prefix is not a directory.

     [ENAMETOOLONG]	A component of a pathname exceeded {NAME_MAX} characters, or an entire path name exceeded {PATH_MAX} characters.

     [ENOENT]		The named file does not exist.

     [EACCES]		Search permission is denied for a component of the path prefix.

     [ELOOP]		Too many symbolic links were encountered in translating the pathname.

     [EPERM]		The effective user ID does not match the owner of the file and the effective user ID is not the super-user, or the effec-
			tive user ID is not the super-user and one or more of the super-user-only flags for the named file would be changed.

     [EOPNOTSUPP]	The named file resides on a file system that does not support file flags.

     [EROFS]		The named file resides on a read-only file system.

     [EFAULT]		path points outside the process's allocated address space.

     [EIO]		An I/O error occurred while reading from or writing to the file system.

     fchflags() will fail if:

     [EBADF]		The descriptor is not valid.

     [EINVAL]		fd refers to a socket, not to a file.

     [EPERM]		The effective user ID does not match the owner of the file and the effective user ID is not the super-user, or the effec-
			tive user ID is not the super-user and one or more of the super-user-only flags for the file would be changed.

     [EOPNOTSUPP]	The file resides on a file system that does not support file flags.

     [EROFS]		The file resides on a read-only file system.

     [EIO]		An I/O error occurred while reading from or writing to the file system.

SEE ALSO

     chflags(1), stat(2), stat_flags(3), init(8), mount_union(8)

HISTORY

     The chflags() and fchflags() functions first appeared in 4.4BSD.  The lchflags() function first appeared in NetBSD 1.5.

BSD
								  August 6, 2011							       BSD