mkdir(2) System Calls Manual mkdir(2)
NAME
mkdir - make a directory file
SYNOPSIS
DESCRIPTION
The system call creates a new directory file named by path. The file permission bits of the new directory are initialized from mode, and
are modified by the process's file mode creation mask. For each bit set in the process's file mode creation mask, the corresponding bit in
the new directory's mode is cleared (see umask(2)).
The directory's owner ID is set to the process's effective-user-ID. If the set-group-ID bit of the parent directory is set, the direc-
tory's group ID is set to the group ID of the parent directory. Otherwise, the directory's group ID is set to the process's effective-
group-ID. The set-group-ID bit of the new directory is set to the same value as the set-group-ID bit of the parent directory.
Symbolic constants defining the access permission bits are found in the header and are used to construct the argument mode. The value of
the argument mode is the bitwise inclusive OR of the values of the desired permissions.
Read by owner.
Write by owner.
Execute (search) by owner.
Read by group.
Write by group.
Execute (search) by group.
Read by others (that is, anybody else).
Write by others.
Execute (search) by others.
Access Control Lists - HFS File Systems Only
On HFS file systems implementing access control lists, the directory is created with three base ACL entries, corresponding to the file
access permission bits (see acl(5)).
Access Control Lists - JFS File Systems Only
On JFS file systems that support access control lists, optional ACL entries are created corresponding to the parent directory's default ACL
entries. Also, the parent directory's default ACL entries are copied as the new directory's default ACL entries (see aclv(5)).
RETURN VALUE
returns one of the following values:
Successful completion.
Failure.
An error code is stored in
ERRORS
If fails, no directory is created and is set to one of the following values:
A component of the path prefix denies search permission.
The parent directory of the new directory denies write permission.
User's or group's disk quota block or inode limit
has been reached for this file system.
The named file already exists.
path points outside the process's allocated address space. The reliable detection of this error is implementation dependent.
An I/O error occurred while writing to the file system.
Too many symbolic links are encountered in translating the path name.
The maximum number of links to the parent directory,
would be exceeded.
The length of the specified path name exceeds
bytes, or the length of a component of the path name exceeds bytes while is in effect.
A component of the path prefix does not exist.
Not enough space on the file system.
A component of the path prefix is not a directory.
The named file resides on a read-only file system.
AUTHOR
was developed by the University of California, Berkeley.
SEE ALSO
acl(2), chmod(2), setacl(2), stat(2), umask(2), acl(5), aclv(5), limits(5).
STANDARDS CONFORMANCE
mkdir(2)
Check Out this Related Man Page
chmod(2) System Calls Manual chmod(2)
NAME
chmod(), fchmod() - change file mode access permissions
SYNOPSIS
DESCRIPTION
The and system calls set the access permission portion of the file's mode according to the bit pattern contained in mode. path points to a
path name naming a file. fildes is a file descriptor.
The following symbolic constants representing the access permission bits are defined with the indicated values in and are used to construct
the mode argument. The value of mode is the bit-wise inclusive OR of the values for the desired permissions.
The mode bit (same as is used to enforce file-locking mode (see lockf(2), fcntl(2), and flock(2)) on files that are not group executable.
This might affect future calls to and on such files (see open(2), creat(2), read(2), write(2), and truncate(2)).
The mode bit (sticky bit) has no significance when set on a regular file.
If the path given to contains a symbolic link as the last element, this link is traversed and path name resolution continues. changes the
access mode of the symbolic link's target, rather than the access mode of the link.
Access Control Lists - HFS File Systems Only
All optional entries in a file's access control list are deleted when is executed. (This behavior conforms to the IEEE Standard POSIX
1003.1-1988.) To preserve optional entries in a file's access control list, it is necessary to save and restore them using and (see
getacl(2) and setacl(2)).
To set the permission bits of access control list entries, use instead of
Access Control Lists - JFS File Systems Only
The effective permissions granted by optional entries in a file's access control list may be changed when is executed. In particular,
using to remove read, write and execute permissions from a file's owner, owning group, and all others works as expected, because affects
the entry in the ACL, limiting any access that can be granted to additional users or groups via optional ACL entries. The effect can be
verified by doing a on the file after the and noting that all optional (non-default) ACL entries with nonzero permissions also have the
comment
To set the permission bits of access control list entries, use instead of
For more information on access control list entries, see acl(5) and aclv(5).
Security Restrictions
To change the mode of a file, the effective user ID of the process must match that of the owner of the file or the process must have the
privilege.
If the process does not have the privilege, mode bit is cleared.
If the process does not have privilege, and the effective group ID of the process does not match the group ID of the file, and none of the
group IDs in the supplementary groups list match the group ID of the file, mode bit is cleared.
If the mode bit (sticky bit) is set on a directory, files inside the directory can be renamed or removed only by the owner of the file, the
owner of the directory, or a process with the privilege (even if the modes of the directory would otherwise allow such an operation).
See privileges(5) for more information about privileged access on systems that support fine-grained privileges.
RETURN VALUE
returns the following values:
Successful completion.
Failure.
is set to indicate the error.
ERRORS
If fails, the file mode is unchanged. is set to one of the following values:
Search permission is denied on a component of the path prefix.
path points outside the allocated address space of the process. The reliable detection of this error is implementa-
tion dependent.
path or fildes descriptor does not refer to an appropriate file.
Too many symbolic links were encountered in translating
path.
A component of path exceeds bytes while is in effect or path exceeds bytes.
A component of path or the file named by path does not exist.
A component of the path prefix is not a directory.
The effective user ID does not match that of
the owner of the file or the process does not have privilege.
The named file resides on a read-only file system.
If fails, the file mode is unchanged. is set to one of the following values:
fildes is not a valid file descriptor.
path or fildes descriptor does not refer to an appropriate file.
The effective user ID does not match that of the owner of the file,
and the effective user ID is not that of a user with appropriate privileges.
The named file resides on a read-only file system.
AUTHOR
was developed by AT&T, the University of California, Berkeley, and HP.
was developed by the University of California, Berkeley.
SEE ALSO
chmod(1), getacl(1), chown(2), creat(2), fcntl(2), flock(2), getacl(2), lockf(2), mknod(2), open(2), read(2), setacl(2), truncate(2),
write(2), acl(5), aclv(5), privileges(5).
STANDARDS CONFORMANCE
chmod(2)