MirOS Manual: getmode(3), setmode(3)

SETMODE(3)                 BSD Programmer's Manual                  SETMODE(3)


     getmode, setmode - modify mode bits


     #include <unistd.h>

     getmode(const void *set, mode_t mode);

     void *
     setmode(const char *mode_str);


     The getmode() function returns a copy of the file permission bits mode as
     altered by the values pointed to by set. While only the mode bits are al-
     tered, other parts of the file mode may be examined.

     The setmode() function takes an absolute (octal) or symbolic value, as
     described in chmod(1), as an argument and returns a pointer to mode
     values to be supplied to getmode(). Because some of the symbolic values
     are relative to the file creation mask, setmode() may call umask(2). If
     this occurs, the file creation mask will be restored before setmode() re-
     turns. If the calling program changes the value of its file creation mask
     after calling setmode(), setmode() must be called again if getmode() is
     to modify future file modes correctly.

     If the mode passed to setmode() is invalid, setmode() returns NULL. The
     caller is responsible for freeing the pointer that setmode() returns.


     The setmode() function may fail and set errno for any of the errors
     specified for the library routine malloc(3) or to ERANGE if an invalid
     octal value was specified.


     chmod(1), stat(2), umask(2), malloc(3)


     The getmode() and setmode() functions first appeared in 4.4BSD.

MirOS BSD #10-current            June 9, 1993                                1

Generated on 2017-04-03 16:26:17 by $MirOS: src/scripts/roff2htm,v 1.88 2017/01/29 00:51:06 tg Exp $

These manual pages and other documentation are copyrighted by their respective writers; their source is available at our CVSweb, AnonCVS, and other mirrors. The rest is Copyright © 2002–2017 The MirOS Project, Germany.
This product includes material provided by mirabilos.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.