chflags man page on BSDi

Man page or keyword search:  
man Server   6284 pages
apropos Keyword Search (all sections)
Output format
BSDi logo
[printable version]

CHFLAGS(2)		    BSD Programmer's Manual		    CHFLAGS(2)

NAME
     chflags, fchflags - set file flags

SYNOPSIS
     #include <sys/types.h>
     #include <sys/stat.h>

     int
     chflags(const char *path, unsigned long flags);

     int
     fchflags(int fd, unsigned long flags);

DESCRIPTION
     The file whose name is given by path or referenced by the descriptor fd
     has its flags changed to flags.

     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 directory is opaque when viewed through a union
			 stack.
	   SF_IMMUTABLE	 The file may not be changed.
	   SF_APPEND	 The file may only be appended to.

     The ``UF_IMMUTABLE'' and ``UF_APPEND'' flags may be set or unset by ei-
     ther the owner of a file or the super-user.

     The ``SF_IMMUTABLE'' and ``SF_APPEND'' flags may only be set or unset by
     the super-user.  Attempts by the non-super-user to set the super-user on-
     ly flags are silently ignored.  These flags may be set at any time, but
     normally may only be unset when the system is in single-user mode.	 (See
     init(8) for details.)

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

ERRORS
     Chflags() will fail it:

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

     [EINVAL]	   The pathname contains a character with the high-order bit
		   set.

     [ENAMETOOLONG]
		   A component of a pathname exceeded 255 characters, or an
		   entire path name exceeded 1023 characters.

     [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 translating 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.

     [EROFS]	   The named file resides on a read-only file system.

     [EFAULT]	   Path points outside the process's allocated address space.

     [EIO]	   An I/O error occurred while reading from or writing to the
		   file system.

     Fchflags() will fail if:

     [EBADF]	   The descriptor is not valid.

     [EINVAL]	   Fd refers to a socket, not to a file.

     [EPERM]	   The effective user ID does not match the owner of the file
		   and the effective user ID is not the super-user.

     [EROFS]	   The file resides on a read-only file system.

     [EIO]	   An I/O error occurred while reading from or writing to the
		   file system.

SEE ALSO
     chflags(1),  init(8),  mount_union(8)

HISTORY
     The chflags and fchflags functions first appeared in 4.4BSD.

BSDI BSD/OS			  May 2, 1995				     2
[top]

List of man pages available for BSDi

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net