CHFLAGS(2)                NetBSD System Calls Manual                CHFLAGS(2)

     chflags, lchflags, fchflags -- set file flags

     Standard C Library (libc, -lc)

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

     chflags(const char *path, u_long flags);

     lchflags(const char *path, u_long flags);

     fchflags(int fd, u_long flags);

     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.  These flags may be set at any time, but nor-
     mally may only be unset when the system is in single-user mode.  (See
     init(8) for details.)

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

     chflags() will fail if:

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

     [ENAMETOOLONG]     A component of a pathname exceeded {NAME_MAX} charac-
                        ters, or an entire path name exceeded {PATH_MAX} char-

     [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 translat-
                        ing 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 effective 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