Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #210
Difficulty: Easy
Routing protocols like OSPF calculate the shortest route to a destination through the network based on a computer algorithm.
True or False?
Linux & Unix Commands - Search Man Pages

mkdir(2) [bsd man page]

MKDIR(2)							System Calls Manual							  MKDIR(2)

NAME
mkdir - make a directory file SYNOPSIS
mkdir(path, mode) char *path; int mode; DESCRIPTION
Mkdir 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; see umask(2)). 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. See umask(2). RETURN VALUE
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: [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] A component of the path prefix 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 path argument contains a byte with the high-order bit set. [EROFS] The named file resides on a read-only file system. [EEXIST] The named file exists. [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 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 direc- tory has been exhausted. [EDQUOT] The user's quota of inodes on the file system on which the directory is being created has been exhausted. [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. [EFAULT] Path points outside the process's allocated address space. SEE ALSO
chmod(2), stat(2), umask(2) 4.2 Berkeley Distribution August 26, 1985 MKDIR(2)

Check Out this Related Man Page

MKFIFO(2)						      BSD System Calls Manual							 MKFIFO(2)

NAME
mkfifo -- make a fifo file SYNOPSIS
#include <sys/types.h> #include <sys/stat.h> int mkfifo(const char *path, mode_t mode); DESCRIPTION
Mkfifo() creates a new fifo file with name path. The access permissions are specified by mode and restricted by the umask(2) of the calling process. The fifo's owner ID is set to the process's effective user ID. The fifo's group ID is set to that of the parent directory in which it is created. RETURN VALUES
A 0 return value indicates success. A -1 return value indicates an error, and an error code is stored in errno. ERRORS
Mkfifo() will fail and no fifo will be created if: [ENOTSUP] The kernel has not been configured to support fifo's. [ENOTDIR] A component of the path prefix is not a directory. [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. [EACCES] Search permission is denied for a component of the path prefix. [ELOOP] Too many symbolic links were encountered in translating the pathname. [EROFS] The named file resides on a read-only file system. [EEXIST] The named file exists. [ENOSPC] The directory in which the entry for the new fifo is being placed cannot be extended because there is no space left on the file system containing the directory. [ENOSPC] There are no free inodes on the file system on which the fifo is being created. [EDQUOT] The directory in which the entry for the new fifo 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 user's quota of inodes on the file system on which the fifo is being created has been exhausted. [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. [EFAULT] Path points outside the process's allocated address space. SEE ALSO
chmod(2), stat(2), umask(2) STANDARDS
The mkfifo function call conforms to IEEE Std 1003.1-1988 (``POSIX.1''). BSD
June 4, 1993 BSD

Featured Tech Videos