Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #771
Difficulty: Medium
Arcade system boards have been using specialized graphics chips since the 1970s.
True or False?
Linux & Unix Commands - Search Man Pages

setquota(2) [bsd man page]

SETQUOTA(2)							System Calls Manual						       SETQUOTA(2)

NAME
setquota - enable/disable quotas on a file system SYNOPSIS
setquota(special, file) char *special, *file; DESCRIPTION
Disc quotas are enabled or disabled with the setquota call. Special indicates a block special device on which a mounted file system exists. If file is nonzero, it specifies a file in that file system from which to take the quotas. If file is 0, then quotas are disabled on the file system. The quota file must exist; it is normally created with the quotacheck(8) program. Only the super-user may turn quotas on or off. SEE ALSO
quota(2), quotacheck(8), quotaon(8) RETURN VALUE
A 0 return value indicates a successful call. A value of -1 is returned when an error occurs and errno is set to indicate the reason for failure. ERRORS
Setquota will fail when one of the following occurs: [ENOTDIR] A component of either path prefix is not a directory. [EINVAL] Either pathname contains a character with the high-order bit set. [EINVAL] The kernel has not been compiled with the QUOTA option. [ENAMETOOLONG] A component of either pathname exceeded 255 characters, or the entire length of either path name exceeded 1023 characters. [ENODEV] Special does not exist. [ENOENT] File does not exist. [ELOOP] Too many symbolic links were encountered in translating either pathname. [EPERM] The caller is not the super-user. [ENOTBLK] Special is not a block device. [ENXIO] The major device number of special is out of range (this indicates no device driver exists for the associated hardware). [EROFS] File resides on a read-only file system. [EACCES] Search permission is denied for a component of either path prefix. [EACCES] File resides on a file system different from special. [EACCES] File is not a plain file. [EIO] An I/O error occurred while reading from or writing to the file containing the quotas. [EFAULT] Special or path points outside the process's allocated address space. BUGS
The error codes are in a state of disarray; too many errors appear to the caller as one value. 4.2 Berkeley Distribution August 26, 1985 SETQUOTA(2)

Check Out this Related Man Page

MKNOD(2)							System Calls Manual							  MKNOD(2)

NAME
mknod - make a special file SYNOPSIS
mknod(path, mode, dev) char *path; int mode, dev; DESCRIPTION
Mknod creates a new file whose name is path. The mode of the new file (including special file bits) is initialized from mode. (The pro- tection part of the mode is modified by the process's mode mask (see umask(2))). The first block pointer of the i-node is initialized from dev and is used to specify which device the special file refers to. If mode indicates a block or character special file, dev is a configuration dependent specification of a character or block I/O device. If mode does not indicate a block special or character special device, dev is ignored. Mknod may be invoked only by the super-user. RETURN VALUE
Upon successful completion a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error. ERRORS
Mknod will fail and the file mode will be unchanged 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 process's effective user ID is not super-user. [EPERM] The pathname contains a character with the high-order bit set. [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 node 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 node is being created. [EDQUOT] The directory in which the entry for the new node 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 node is being created has been exhausted. [EROFS] The named file resides on a read-only file system. [EEXIST] The named file exists. [EFAULT] Path points outside the process's allocated address space. SEE ALSO
chmod(2), stat(2), umask(2) 4th Berkeley Distribution May 23, 1986 MKNOD(2)

Featured Tech Videos