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
46 .Fn chflags "const char *path" "unsigned long flags"
48 .Fn lchflags "const char *path" "unsigned long flags"
50 .Fn fchflags "int fd" "unsigned long flags"
52 .Fn chflagsat "int fd" "const char *path" "unsigned long flags" "int atflag"
57 or referenced by the descriptor
59 has its flags changed to
66 except in the case where the named file is a symbolic link,
69 will change the flags of the link itself,
70 rather than the file it points to.
74 is equivalent to either
80 except in the case where
82 specifies a relative path.
83 In this case the file to be changed is determined relative to the directory
84 associated with the file descriptor
86 instead of the current working directory.
89 are constructed by a bitwise-inclusive OR of flags from the following list,
92 .Bl -tag -width indent
93 .It Dv AT_SYMLINK_NOFOLLOW
96 names a symbolic link, then the flags of the symbolic link are changed.
98 Only allow to change flags for a file which is beneath of
99 the starting directory.
104 is passed the special value
108 parameter, the current working directory is used.
111 is zero, the behavior is identical to a call to
114 The flags specified are formed by
118 .Bl -tag -width ".Dv SF_IMMUTABLE" -compact -offset indent
120 The file may only be appended to.
122 The file has been archived.
123 This flag means the opposite of the DOS, Windows and CIFS
124 FILE_ATTRIBUTE_ARCHIVE attribute.
125 This flag has been deprecated, and may be removed in a future release.
127 The file may not be changed.
129 The file may not be renamed or deleted.
131 The file is a snapshot file.
133 The file may only be appended to.
135 The file needs to be archived.
136 This flag has the same meaning as the DOS, Windows and CIFS
137 FILE_ATTRIBUTE_ARCHIVE attribute.
138 Filesystems in FreeBSD may or may not have special handling for this flag.
139 For instance, ZFS tracks changes to files and will set this bit when a
141 UFS only stores the flag, and relies on the application to change it when
144 The file may be hidden from directory listings at the application's
146 The file has the DOS, Windows and CIFS FILE_ATTRIBUTE_HIDDEN attribute.
148 The file may not be changed.
150 Do not dump the file.
152 The file may not be renamed or deleted.
154 The file is offline, or has the Windows and CIFS FILE_ATTRIBUTE_OFFLINE
156 Filesystems in FreeBSD store and display this flag, but do not provide any
157 special handling when it is set.
159 The directory is opaque when viewed through a union stack.
161 The file is read only, and may not be written or appended.
162 Filesystems may use this flag to maintain compatibility with the DOS, Windows
163 and CIFS FILE_ATTRIBUTE_READONLY attribute.
165 The file contains a Windows reparse point and has the Windows and CIFS
166 FILE_ATTRIBUTE_REPARSE_POINT attribute.
168 The file has the Windows FILE_ATTRIBUTE_SPARSE_FILE attribute.
169 This may also be used by a filesystem to indicate a sparse file.
171 The file has the DOS, Windows and CIFS FILE_ATTRIBUTE_SYSTEM attribute.
172 Filesystems in FreeBSD may store and display this flag, but do not provide
173 any special handling when it is set.
177 .Dv SF_IMMUTABLE , SF_APPEND ,
180 is set a non-super-user cannot change any flags and even the super-user
181 can change flags only if securelevel is 0.
187 .Dv UF_IMMUTABLE , UF_APPEND , UF_NOUNLINK , UF_NODUMP ,
190 flags may be set or unset by either the owner of a file or the super-user.
193 .Dv SF_IMMUTABLE , SF_APPEND , SF_NOUNLINK ,
196 flags may only be set or unset by the super-user.
197 Attempts to toggle these flags by non-super-users are rejected.
198 These flags may be set at any time, but normally may only be unset when
199 the system is in single-user mode.
204 The implementation of all flags is filesystem-dependent.
205 See the description of the
207 flag above for one example of the differences in behavior.
208 Care should be exercised when writing applications to account for
209 support or lack of support of these flags in various filesystems.
213 flag is maintained by the system and cannot be toggled.
219 system call will fail if:
222 A component of the path prefix is not a directory.
223 .It Bq Er ENAMETOOLONG
224 A component of a pathname exceeded 255 characters,
225 or an entire path name exceeded 1023 characters.
227 The named file does not exist.
229 Search permission is denied for a component of the path prefix.
231 Too many symbolic links were encountered in translating the pathname.
233 The effective user ID does not match the owner of the file and
234 the effective user ID is not the super-user.
237 .Dv SF_IMMUTABLE , SF_APPEND ,
240 is set and the user is either not the super-user or
241 securelevel is greater than 0.
243 A non-super-user attempted to toggle one of
244 .Dv SF_ARCHIVED , SF_IMMUTABLE , SF_APPEND ,
248 An attempt was made to toggle the
252 The named file resides on a read-only file system.
257 points outside the process's allocated address space.
261 error occurred while reading from or writing to the file system.
263 The underlying file system does not support file flags, or
264 does not support all of the flags set in
270 system call will fail if:
273 The descriptor is not valid.
278 refers to a socket, not to a file.
280 The effective user ID does not match the owner of the file and
281 the effective user ID is not the super-user.
284 .Dv SF_IMMUTABLE , SF_APPEND ,
287 is set and the user is either not the super-user or
288 securelevel is greater than 0.
290 A non-super-user attempted to toggle one of
291 .Dv SF_ARCHIVED , SF_IMMUTABLE , SF_APPEND ,
295 An attempt was made to toggle the
299 The file resides on a read-only file system.
303 error occurred while reading from or writing to the file system.
305 The underlying file system does not support file flags, or
306 does not support all of the flags set in
308 .It Bq Er ENOTCAPABLE
311 flag was specified but
313 is not strictly relative to the starting directory.
316 is absolute or includes a ".." component that escapes the starting directory.
329 system calls first appeared in
333 system call first appeared in
337 system call first appeared in