CHMOD(3)                   POSIX Programmer's Manual                  CHMOD(3)



PPRROOLLOOGG
       This manual page is part of the POSIX Programmer's Manual.  The OS
       implementation of this interface may differ (consult the corresponding
       OS manual page for details of OS behavior), or the interface may not be
       implemented on OS.


NNAAMMEE
       chmod, fchmodat -- change mode of a file relative to directory file
       descriptor

SSYYNNOOPPSSIISS
       #include <sys/stat.h>

       int chmod(const char *_p_a_t_h, mode_t _m_o_d_e);
       int fchmodat(int _f_d, const char *_p_a_t_h, mode_t _m_o_d_e, int _f_l_a_g);

DDEESSCCRRIIPPTTIIOONN
       The _c_h_m_o_d() function shall change S_ISUID, S_ISGID, S_ISVTX, and the
       file permission bits of the file named by the pathname pointed to by
       the _p_a_t_h argument to the corresponding bits in the _m_o_d_e argument. The
       application shall ensure that the effective user ID of the process
       matches the owner of the file or the process has appropriate privileges
       in order to do this.

       S_ISUID, S_ISGID, S_ISVTX, and the file permission bits are described
       in _<_s_y_s_/_s_t_a_t_._h_>.

       If the calling process does not have appropriate privileges, and if the
       group ID of the file does not match the effective group ID or one of
       the supplementary group IDs and if the file is a regular file, bit
       S_ISGID (set-group-ID on execution) in the file's mode shall be cleared
       upon successful return from _c_h_m_o_d().

       Additional implementation-defined restrictions may cause the S_ISUID
       and S_ISGID bits in _m_o_d_e to be ignored.

       Upon successful completion, _c_h_m_o_d() shall mark for update the last file
       status change timestamp of the file.

       The _f_c_h_m_o_d_a_t() function shall be equivalent to the _c_h_m_o_d() function
       except in the case where _p_a_t_h specifies a relative path. In this case
       the file to be changed is determined relative to the directory
       associated with the file descriptor _f_d instead of the current working
       directory. If the file descriptor was opened without O_SEARCH, the
       function shall check whether directory searches are permitted using the
       current permissions of the directory underlying the file descriptor. If
       the file descriptor was opened with O_SEARCH, the function shall not
       perform the check.

       Values for _f_l_a_g are constructed by a bitwise-inclusive OR of flags from
       the following list, defined in _<_f_c_n_t_l_._h_>:

       AT_SYMLINK_NOFOLLOW
             If _p_a_t_h names a symbolic link, then the mode of the symbolic link
             is changed.

       If _f_c_h_m_o_d_a_t() is passed the special value AT_FDCWD in the _f_d parameter,
       the current working directory shall be used. If also _f_l_a_g is zero, the
       behavior shall be identical to a call to _c_h_m_o_d().

RREETTUURRNN VVAALLUUEE
       Upon successful completion, these functions shall return 0.  Otherwise,
       these functions shall return -1 and set _e_r_r_n_o to indicate the error. If
       -1 is returned, no change to the file mode occurs.

EERRRROORRSS
       These functions shall fail if:

       EEAACCCCEESS Search permission is denied on a component of the path prefix.

       EELLOOOOPP  A loop exists in symbolic links encountered during resolution of
              the _p_a_t_h argument.

       EENNAAMMEETTOOOOLLOONNGG
              The length of a component of a pathname is longer than
              {NAME_MAX}.

       EENNOOEENNTT A component of _p_a_t_h does not name an existing file or _p_a_t_h is an
              empty string.

       EENNOOTTDDIIRR
              A component of the path prefix names an existing file that is
              neither a directory nor a symbolic link to a directory, or the
              _p_a_t_h argument contains at least one non-<slash> character and
              ends with one or more trailing <slash> characters and the last
              pathname component names an existing file that is neither a
              directory nor a symbolic link to a directory.

       EEPPEERRMM  The effective user ID does not match the owner of the file and
              the process does not have appropriate privileges.

       EERROOFFSS  The named file resides on a read-only file system.

       The _f_c_h_m_o_d_a_t() function shall fail if:

       EEAACCCCEESS _f_d was not opened with O_SEARCH and the permissions of the
              directory underlying _f_d do not permit directory searches.

       EEBBAADDFF  The _p_a_t_h argument does not specify an absolute path and the _f_d
              argument is neither AT_FDCWD nor a valid file descriptor open
              for reading or searching.

       EENNOOTTDDIIRR
              The _p_a_t_h argument is not an absolute path and _f_d is a file
              descriptor associated with a non-directory file.

       These functions may fail if:

       EEIINNTTRR  A signal was caught during execution of the function.

       EEIINNVVAALL The value of the _m_o_d_e argument is invalid.

       EELLOOOOPP  More than {SYMLOOP_MAX} symbolic links were encountered during
              resolution of the _p_a_t_h argument.

       EENNAAMMEETTOOOOLLOONNGG
              The length of a pathname exceeds {PATH_MAX}, or pathname
              resolution of a symbolic link produced an intermediate result
              with a length that exceeds {PATH_MAX}.

       The _f_c_h_m_o_d_a_t() function may fail if:

       EEIINNVVAALL The value of the _f_l_a_g argument is invalid.

       EEOOPPNNOOTTSSUUPPPP
              The AT_SYMLINK_NOFOLLOW bit is set in the _f_l_a_g argument, _p_a_t_h
              names a symbolic link, and the system does not support changing
              the mode of a symbolic link.

       _T_h_e _f_o_l_l_o_w_i_n_g _s_e_c_t_i_o_n_s _a_r_e _i_n_f_o_r_m_a_t_i_v_e_.

EEXXAAMMPPLLEESS
   SSeettttiinngg RReeaadd PPeerrmmiissssiioonnss ffoorr UUsseerr,, GGrroouupp,, aanndd OOtthheerrss
       The following example sets read permissions for the owner, group, and
       others.

           ##iinncclluuddee <<ssyyss//ssttaatt..hh>>

           const char *path;
           ...
           chmod(path, S_IRUSR|S_IRGRP|S_IROTH);

   SSeettttiinngg RReeaadd,, WWrriittee,, aanndd EExxeeccuuttee PPeerrmmiissssiioonnss ffoorr tthhee OOwwnneerr OOnnllyy
       The following example sets read, write, and execute permissions for the
       owner, and no permissions for group and others.

           ##iinncclluuddee <<ssyyss//ssttaatt..hh>>

           const char *path;
           ...
           chmod(path, S_IRWXU);

   SSeettttiinngg DDiiffffeerreenntt PPeerrmmiissssiioonnss ffoorr OOwwnneerr,, GGrroouupp,, aanndd OOtthheerr
       The following example sets owner permissions for CHANGEFILE to read,
       write, and execute, group permissions to read and execute, and other
       permissions to read.

           ##iinncclluuddee <<ssyyss//ssttaatt..hh>>

           #define CHANGEFILE "/etc/myfile"
           ...
           chmod(CHANGEFILE, S_IRWXU|S_IRGRP|S_IXGRP|S_IROTH);

   SSeettttiinngg aanndd CChheecckkiinngg FFiillee PPeerrmmiissssiioonnss
       The following example sets the file permission bits for a file named
       //hhoommee//ccnndd//mmoodd11, then calls the _s_t_a_t() function to verify the
       permissions.

           ##iinncclluuddee <<ssyyss//ttyyppeess..hh>>
           ##iinncclluuddee <<ssyyss//ssttaatt..hh>>

           int status;
           struct stat buffer
           ...
           chmod("home/cnd/mod1", S_IRWXU|S_IRWXG|S_IROTH|S_IWOTH);
           status = stat("home/cnd/mod1", &buffer;);

AAPPPPLLIICCAATTIIOONN UUSSAAGGEE
       In order to ensure that the S_ISUID and S_ISGID bits are set, an
       application requiring this should use _s_t_a_t() after a successful _c_h_m_o_d()
       to verify this.

       Any file descriptors currently open by any process on the file could
       possibly become invalid if the mode of the file is changed to a value
       which would deny access to that process. One situation where this could
       occur is on a stateless file system. This behavior will not occur in a
       conforming environment.

RRAATTIIOONNAALLEE
       This volume of POSIX.1-2008 specifies that the S_ISGID bit is cleared
       by _c_h_m_o_d() on a regular file under certain conditions. This is
       specified on the assumption that regular files may be executed, and the
       system should prevent users from making executable _s_e_t_g_i_d() files
       perform with privileges that the caller does not have. On
       implementations that support execution of other file types, the S_ISGID
       bit should be cleared for those file types under the same
       circumstances.

       Implementations that use the S_ISUID bit to indicate some other
       function (for example, mandatory record locking) on non-executable
       files need not clear this bit on writing. They should clear the bit for
       executable files and any other cases where the bit grants special
       powers to processes that change the file contents. Similar comments
       apply to the S_ISGID bit.

       The purpose of the _f_c_h_m_o_d_a_t() function is to enable changing the mode
       of files in directories other than the current working directory
       without exposure to race conditions.  Any part of the path of a file
       could be changed in parallel to a call to _c_h_m_o_d(), resulting in
       unspecified behavior. By opening a file descriptor for the target
       directory and using the _f_c_h_m_o_d_a_t() function it can be guaranteed that
       the changed file is located relative to the desired directory. Some
       implementations might allow changing the mode of symbolic links. This
       is not supported by the interfaces in the POSIX specification. Systems
       with such support provide an interface named _l_c_h_m_o_d().  To support such
       implementations _f_c_h_m_o_d_a_t() has a _f_l_a_g parameter.

FFUUTTUURREE DDIIRREECCTTIIOONNSS
       None.

SSEEEE AALLSSOO
       _a_c_c_e_s_s(), _c_h_o_w_n(), _e_x_e_c, _f_s_t_a_t_a_t(), _f_s_t_a_t_v_f_s(), _m_k_d_i_r(), _m_k_f_i_f_o(),
       _m_k_n_o_d(), _o_p_e_n()

       The Base Definitions volume of POSIX.1-2008, <<ffccnnttll..hh>>, <<ssyyss__ssttaatt..hh>>,
       <<ssyyss__ttyyppeess..hh>>

CCOOPPYYRRIIGGHHTT
       Portions of this text are reprinted and reproduced in electronic form
       from IEEE Std 1003.1, 2013 Edition, Standard for Information Technology
       -- Portable Operating System Interface (POSIX), The Open Group Base
       Specifications Issue 7, Copyright (C) 2013 by the Institute of
       Electrical and Electronics Engineers, Inc and The Open Group.  (This is
       POSIX.1-2008 with the 2013 Technical Corrigendum 1 applied.) In the
       event of any discrepancy between this version and the original IEEE and
       The Open Group Standard, the original IEEE and The Open Group Standard
       is the referee document. The original Standard can be obtained online
       at http://www.unix.org/online.html .

       Any typographical or formatting errors that appear in this page are
       most likely to have been introduced during the conversion of the source
       files to man page format. To report such errors, see
       https://www.kernel.org/doc/man-pages/reporting_bugs.html .



IEEE/The Open Group                  2013                             CHMOD(3)
