1 .\" Copyright (c) 1989, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" @(#)chflags.2 8.3 (Berkeley) 5/2/95
29 .\" $FreeBSD: src/lib/libc/sys/chflags.2,v 1.11.2.7 2001/12/14 18:34:00 ru Exp $
30 .\" $DragonFly: src/lib/libc/sys/chflags.2,v 1.5 2008/11/11 00:55:49 pavalos Exp $
46 .Fn chflags "const char *path" "u_long flags"
48 .Fn lchflags "const char *path" "u_long flags"
50 .Fn fchflags "int fd" "u_long flags"
55 or referenced by the descriptor
57 has its flags changed to
64 except in the case where the named file is a symbolic link,
67 will change the flags of the link itself,
68 rather than the file it points to.
70 The flags specified are formed by
74 .Bl -tag -width "SF_IMMUTABLE" -compact -offset indent
78 The file may not be changed.
80 The file may only be appended to.
82 The directory is opaque when viewed through a union stack.
84 The file may not be renamed or deleted.
86 Do not retain history for file.
91 The flag is recursive and need only be set on a top-level directory.
93 The file may be archived.
95 The file may not be changed.
97 The file may only be appended to.
99 The file may not be renamed or deleted.
101 Do not retain history for file.
106 The flag is recursive and need only be set on a top-level directory.
112 flags may be set or unset by either the owner of a file or the super-user.
117 flags may only be set or unset by the super-user.
118 Attempts by the non-super-user to set the super-user only flags
119 are silently ignored.
120 These flags may be set at any time, but normally may only be unset when
121 the system is in single-user mode.
132 A component of the path prefix is not a directory.
133 .It Bq Er ENAMETOOLONG
134 A component of a pathname exceeded 255 characters,
135 or an entire path name exceeded 1023 characters.
137 The named file does not exist.
139 Search permission is denied for a component of the path prefix.
141 Too many symbolic links were encountered in translating the pathname.
143 The effective user ID does not match the owner of the file and
144 the effective user ID is not the super-user.
146 The named file resides on a read-only file system.
149 points outside the process's allocated address space.
153 error occurred while reading from or writing to the file system.
155 The underlying file system does not support file flags.
162 The descriptor is not valid.
165 refers to a socket, not to a file.
167 The effective user ID does not match the owner of the file and
168 the effective user ID is not the super-user.
170 The file resides on a read-only file system.
174 error occurred while reading from or writing to the file system.
176 The underlying file system does not support file flags.
190 functions first appeared in