link(2) [opendarwin man page]
LINK(2) BSD System Calls Manual LINK(2) NAME
link -- make a hard file link SYNOPSIS
#include <unistd.h> int link(const char *name1, const char *name2); DESCRIPTION
The link() function call atomically creates the specified directory entry (hard link) name2 with the attributes of the underlying object pointed at by name1 If the link is successful: the link count of the underlying object is incremented; name1 and name2 share equal access and rights to the underlying object. If name1 is removed, the file name2 is not deleted and the link count of the underlying object is decremented. Name1 must exist for the hard link to succeed and both name1 and name2 must be in the same file system. As mandated by POSIX.1 name1 may not be a directory. RETURN VALUES
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
Link() will fail and no link will be created if: [ENOTDIR] A component of either 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 either path prefix does not exist. [EACCES] A component of either path prefix denies search permission. [EACCES] The requested link requires writing in a directory with a mode that denies write permission. [ELOOP] Too many symbolic links were encountered in translating one of the pathnames. [ENOENT] The file named by name1 does not exist. [EEXIST] The link named by name2 does exist. [EPERM] The file named by name1 is a directory. [EXDEV] The link named by name2 and the file named by name1 are on different file systems. [ENOSPC] The directory in which the entry for the new link is being placed cannot be extended because there is no space left on the file system containing the directory. [EDQUOT] The directory in which the entry for the new link is being placed cannot be extended because the user's quota of disk blocks on the file system containing the directory has been exhausted. [EIO] An I/O error occurred while reading from or writing to the file system to make the directory entry. [EROFS] The requested link requires writing in a directory on a read-only file system. [EFAULT] One of the pathnames specified is outside the process's allocated address space. SEE ALSO
symlink(2), unlink(2) STANDARDS
The link() function is expected to conform to IEEE Std 1003.1-1988 (``POSIX.1''). 4th Berkeley Distribution January 12, 1994 4th Berkeley Distribution
Check Out this Related Man Page
symlink(2) System Calls Manual symlink(2) Name symlink - make symbolic link to a file Syntax symlink(name1, name2) char *name1, *name2; Description A symbolic link name2 is created to name1 (name2 is the name of the file created, name1 is the string used in creating the symbolic link). Either name can be an arbitrary path name. The files need not be on the same file system. Return Values Upon successful completion, a zero (0) value is returned. If an error occurs, the error code is stored in errno, and a -1 value is returned. Diagnostics The symbolic link is made, unless one or more of the following are true: [ENOTDIR] A component of the name2 prefix is not a directory. [EEXIST] The name2 already exists. [EACCES] A component of the name2 path prefix denies search permission. [EROFS] The file name2 would reside on a read-only file system. [EFAULT] The name1 or name2 points outside the process's allocated address space. [ELOOP] Too many symbolic links were encountered in translating the pathname. [ENAMETOOLONG] A component of either pathname exceeded MAXNAMELEN characters, or the entire length of either pathname exceeded MAXPATHNAME characters. [ENOENT] The named file does not exist. [EIO] An I/O error occurred while making the directory entry for name2, or allocating the inode for name2, or writing out the link contents of name2. [ENOSPC] The directory in which the entry for the new symbolic link is being placed cannot be extended, because there is no space left on the file system containing the directory. [ENOSPC] The new symbolic link cannot be created, because there is no space left on the file system that will contain the symbolic link. [ENOSPC] There are no free inodes on the file system on which the symbolic link is being created. [EDQUOT] The directory in which the entry for the new symbolic link 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 symbolic link cannot be created because the user's quota of disk blocks on the file system that will contain the symbolic link has been exhausted. [EDQUOT] The user's quota of inodes on the file system on which the user's symbolic link is being created has been exhausted. [EIO] An I/O error occurred while making the directory entry or allocating the inode. [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. See Also ln(1), link(2), readlink(2), stat(2), unlink(2) symlink(2)