mkdir(2) [osx man page]
MKDIR(2) BSD System Calls Manual MKDIR(2) NAME
mkdir -- make a directory file SYNOPSIS
#include <sys/stat.h> int mkdir(const char *path, mode_t mode); DESCRIPTION
The directory path is created with the access permissions specified by mode and restricted by the umask(2) of the calling process. See chmod(2) for the possible permission bit masks for mode. The directory's owner ID is set to the process's effective user ID. The directory's group ID is set to that of the parent directory in which it is created. Note: the behavior of mkdir() is undefined when mode bits other than the low 9 bits are used. Use chmod(2) after mkdir() to explicitly set the other bits (See example below). RETURN VALUES
A 0 return value indicates success. A -1 return value indicates an error, and an error code is stored in errno. ERRORS
Mkdir() will fail and no directory will be created if: [EACCES] Search permission is denied for a component of the path prefix. [EACCES] Write permission is denied for the parent directory. [EDQUOT] The new directory cannot be created because the user's quota of disk blocks on the file system that will contain the directory has been exhausted. [EDQUOT] The user's quota of inodes on the file system on which the directory is being created has been exhausted. [EEXIST] The named file exists. [EFAULT] Path points outside the process's allocated address space. [EIO] An I/O error occurred while making the directory entry or allocating the inode. [EIO] An I/O error occurred while reading from or writing to the file system. [ELOOP] Too many symbolic links were encountered in translating the pathname. This is taken to be indicative of a looping sym- bolic link. [EMLINK] The parent directory already has {LINK_MAX} links. [ENAMETOOLONG] A component of a pathname exceeded {NAME_MAX} characters, or an entire path name exceeded {PATH_MAX} characters. [ENOENT] A component of the path prefix does not exist or path is an empty string. [ENOSPC] The new directory cannot be created because there is no space left on the file system that would contain it. [ENOSPC] There are no free inodes on the file system on which the directory is being created. [ENOTDIR] A component of the path prefix is not a directory. [EROFS] The parent directory resides on a read-only file system. EXAMPLE
int main (int argc, const char * argv[]) { /* The behavior of mkdir is undefined for anything other than the "permission" bits */ if (mkdir("/tmp/blah", 0777)) perror("/tmp/blah"); /* So we need to set the sticky/executable bits explicitly with chmod after calling mkdir */ if (chmod("/tmp/blah", 07777)) perror("/tmp/blah"); } LEGACY SYNOPSIS
#include <sys/types.h> #include <sys/stat.h> The include file <sys/types.h> is necessary. SEE ALSO
chmod(2), stat(2), umask(2), compat(5) STANDARDS
The mkdir() function conforms to IEEE Std 1003.1-1988 (``POSIX.1''). 4.2 Berkeley Distribution December 11, 1993 4.2 Berkeley Distribution
Check Out this Related Man Page
mkdir(2) System Calls Manual mkdir(2) Name mkdir - make a directory file Syntax #include <sys/types.h> #include <sys/stat.h> mkdir(path, mode) char *path; mode_t mode; Description The system call creates a new directory file with name path. The mode of the new file is initialized from mode. The protection part of the mode is modified by the process's mode mask. For further information, see The directory's owner ID is set to the process's effective user ID. The directory's group ID is set to that of the parent directory in which it is created. The low-order 9 bits of mode are modified by the process's file mode creation mask: all bits set in the process's file mode creation mask are cleared. For further information, see Return Values A 0 return value indicates success. A -1 return value indicates an error, and an error code is stored in errno. Diagnostics The system call fails and a directory is not created if the following occurs: [EISDIR] The named file is a directory, and the arguments specify it is to be opened for writing. [ENOTDIR] A component of the path prefix is not a directory. [ENAMETOOLONG] A component of a pathname exceeded 255 characters, or an entire pathname exceeded 1023 characters. [ENOENT] A component of the path prefix does not exist or the path argument points to an empty string and the environment defined is POSIX or SYSTEM_FIVE. [EACCES] Search permission is denied for a component of the path prefix, or write permission is denied on the parent directory to be created. [EROFS] The named file resides on a read-only file system. [EEXIST] The named file exists. [EFAULT] The path points outside the process's allocated address space. [ELOOP] Too many symbolic links were encountered in translating the pathname. [EIO] An I/O error occurred while reading from or writing to the file system. [EIO] An I/O error occurred while making the directory entry or allocating the inode. [ENOSPC] The directory in which the entry for the new directory is being placed cannot be extended, because there is no space left on the file system containing the directory. [ENOSPC] The new directory cannot be created, because there is no space left on the file system that will contain the directory. [ENOSPC] There are no free inodes on the file system on which the directory is being created. [EDQUOT] The directory in which the entry for the new directory is being placed cannot be extended, because the user's quota of disk blocks on the file system containing the directory has been exhausted. [EDQUOT] The new directory cannot be created, because the user's quota of disk blocks on the file system that will contain the directory has been exhausted. [EDQUOT] The user's quota of inodes on the file system on which the directory is being created has been exhausted. [ESTALE] The file handle given in the argument is invalid. The file referred to by that file handle no longer exists or has been revoked. [ETIMEDOUT] A "connect" request or remote file operation failed because the connected party did not properly respond after a period of time that is dependent on the communications protocol. [EMLINK] The link count of the parent directory would exceed {LINK_MAX}. See Also chmod(2), stat(2), umask(2) mkdir(2)