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.
97 .It Dv AT_RESOLVE_BENEATH
98 Only walk paths below the directory specified by the
101 See the description of the
102 .Dv O_RESOLVE_BENEATH
110 is passed the special value
114 parameter, the current working directory is used.
117 is zero, the behavior is identical to a call to
120 The flags specified are formed by
124 .Bl -tag -width ".Dv SF_IMMUTABLE" -compact -offset indent
126 The file may only be appended to.
128 The file has been archived.
129 This flag means the opposite of the DOS, Windows and CIFS
130 FILE_ATTRIBUTE_ARCHIVE attribute.
131 This flag has been deprecated, and may be removed in a future release.
133 The file may not be changed.
135 The file may not be renamed or deleted.
137 The file is a snapshot file.
139 The file may only be appended to.
141 The file needs to be archived.
142 This flag has the same meaning as the DOS, Windows and CIFS
143 FILE_ATTRIBUTE_ARCHIVE attribute.
144 Filesystems in FreeBSD may or may not have special handling for this flag.
145 For instance, ZFS tracks changes to files and will set this bit when a
147 UFS only stores the flag, and relies on the application to change it when
150 The file may be hidden from directory listings at the application's
152 The file has the DOS, Windows and CIFS FILE_ATTRIBUTE_HIDDEN attribute.
154 The file may not be changed.
156 Do not dump the file.
158 The file may not be renamed or deleted.
160 The file is offline, or has the Windows and CIFS FILE_ATTRIBUTE_OFFLINE
162 Filesystems in FreeBSD store and display this flag, but do not provide any
163 special handling when it is set.
165 The directory is opaque when viewed through a union stack.
167 The file is read only, and may not be written or appended.
168 Filesystems may use this flag to maintain compatibility with the DOS, Windows
169 and CIFS FILE_ATTRIBUTE_READONLY attribute.
171 The file contains a Windows reparse point and has the Windows and CIFS
172 FILE_ATTRIBUTE_REPARSE_POINT attribute.
174 The file has the Windows FILE_ATTRIBUTE_SPARSE_FILE attribute.
175 This may also be used by a filesystem to indicate a sparse file.
177 The file has the DOS, Windows and CIFS FILE_ATTRIBUTE_SYSTEM attribute.
178 Filesystems in FreeBSD may store and display this flag, but do not provide
179 any special handling when it is set.
183 .Dv SF_IMMUTABLE , SF_APPEND ,
186 is set a non-super-user cannot change any flags and even the super-user
187 can change flags only if securelevel is 0.
193 .Dv UF_IMMUTABLE , UF_APPEND , UF_NOUNLINK , UF_NODUMP ,
196 flags may be set or unset by either the owner of a file or the super-user.
199 .Dv SF_IMMUTABLE , SF_APPEND , SF_NOUNLINK ,
202 flags may only be set or unset by the super-user.
203 Attempts to toggle these flags by non-super-users are rejected.
204 These flags may be set at any time, but normally may only be unset when
205 the system is in single-user mode.
210 The implementation of all flags is filesystem-dependent.
211 See the description of the
213 flag above for one example of the differences in behavior.
214 Care should be exercised when writing applications to account for
215 support or lack of support of these flags in various filesystems.
219 flag is maintained by the system and cannot be toggled.
225 system call will fail if:
228 A component of the path prefix is not a directory.
229 .It Bq Er ENAMETOOLONG
230 A component of a pathname exceeded 255 characters,
231 or an entire path name exceeded 1023 characters.
233 The named file does not exist.
235 Search permission is denied for a component of the path prefix.
237 Too many symbolic links were encountered in translating the pathname.
239 The effective user ID does not match the owner of the file and
240 the effective user ID is not the super-user.
243 .Dv SF_IMMUTABLE , SF_APPEND ,
246 is set and the user is either not the super-user or
247 securelevel is greater than 0.
249 A non-super-user attempted to toggle one of
250 .Dv SF_ARCHIVED , SF_IMMUTABLE , SF_APPEND ,
254 An attempt was made to toggle the
258 The named file resides on a read-only file system.
263 points outside the process's allocated address space.
267 error occurred while reading from or writing to the file system.
269 Corrupted data was detected while reading from the file system.
271 The underlying file system does not support file flags, or
272 does not support all of the flags set in
278 system call will fail if:
281 The descriptor is not valid.
286 refers to a socket, not to a file.
288 The effective user ID does not match the owner of the file and
289 the effective user ID is not the super-user.
292 .Dv SF_IMMUTABLE , SF_APPEND ,
295 is set and the user is either not the super-user or
296 securelevel is greater than 0.
298 A non-super-user attempted to toggle one of
299 .Dv SF_ARCHIVED , SF_IMMUTABLE , SF_APPEND ,
303 An attempt was made to toggle the
307 The file resides on a read-only file system.
311 error occurred while reading from or writing to the file system.
313 Corrupted data was detected while reading from the file system.
315 The underlying file system does not support file flags, or
316 does not support all of the flags set in
318 .It Bq Er ENOTCAPABLE
321 or contained a ".." component leading to a
322 directory outside of the directory hierarchy specified by
324 and the process is in capability mode or the
325 .Dv AT_RESOLVE_BENEATH
339 system calls first appeared in
343 system call first appeared in
347 system call first appeared in