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. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)chflags.2 8.3 (Berkeley) 5/2/95
49 .Fn chflags "const char *path" "u_long flags"
51 .Fn lchflags "const char *path" "int flags"
53 .Fn fchflags "int fd" "u_long flags"
58 or referenced by the descriptor
60 has its flags changed to
67 except in the case where the named file is a symbolic link,
70 will change the flags of the link itself,
71 rather than the file it points to.
73 The flags specified are formed by
77 .Bl -tag -width "SF_IMMUTABLE" -compact -offset indent
81 The file may not be changed.
83 The file may only be appended to.
85 The file may not be renamed or deleted.
87 The directory is opaque when viewed through a union stack.
89 The file may be archived.
91 The file may not be changed.
93 The file may only be appended to.
95 The file may not be renamed or deleted.
97 The file is a snapshot file.
105 is set a non-super-user cannot change any flags and even the super-user
106 can change flags only if securelevel is greater than 0.
118 flags may be set or unset by either the owner of a file or the super-user.
126 flags may only be set or unset by the super-user.
127 Attempts to set these flags by non-super-users are rejected, attempts by
128 non-superusers to clear flags that are already unset are silently ignored.
129 These flags may be set at any time, but normally may only be unset when
130 the system is in single-user mode.
137 flag is maintained by the system and cannot be changed by any user.
143 system call will fail if:
146 A component of the path prefix is not a directory.
147 .It Bq Er ENAMETOOLONG
148 A component of a pathname exceeded 255 characters,
149 or an entire path name exceeded 1023 characters.
151 The named file does not exist.
153 Search permission is denied for a component of the path prefix.
155 Too many symbolic links were encountered in translating the pathname.
157 The effective user ID does not match the owner of the file and
158 the effective user ID is not the super-user.
165 is set and the user is either not the super-user or
166 securelevel is greater than 0.
168 A non-super-user tries to set one of
174 The named file resides on a read-only file system.
179 points outside the process's allocated address space.
183 error occurred while reading from or writing to the file system.
185 The underlying file system does not support file flags.
190 system call will fail if:
193 The descriptor is not valid.
198 refers to a socket, not to a file.
200 The effective user ID does not match the owner of the file and
201 the effective user ID is not the super-user.
208 is set and the user is either not the super-user or
209 securelevel is greater than 0.
211 A non-super-user tries to set one of
217 The file resides on a read-only file system.
221 error occurred while reading from or writing to the file system.
223 The underlying file system does not support file flags.
236 system calls first appeared in