Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #662
Difficulty: Easy
The drives in DOS are referred to by identifying integers.
True or False?
Linux & Unix Commands - Search Man Pages

symlink(2) [osx man page]

SYMLINK(2)						      BSD System Calls Manual							SYMLINK(2)

NAME
symlink -- make symbolic link to a file SYNOPSIS
#include <unistd.h> int symlink(const char *path1, const char *path2); DESCRIPTION
A symbolic link path2 is created to path1 (path2 is the name of the file created, path1 is the string used in creating the symbolic link). Either name may be an arbitrary path name; the files need not be on the same file system. RETURN VALUES
Upon successful completion, a zero value is returned. If an error occurs, the error code is stored in errno and a -1 value is returned. ERRORS
The symbolic link succeeds unless: [EACCES] Write permission is denied in the directory where the symbolic link is being created. [EACCES] A component of the path2 path prefix denies search permission. [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 symbolic link is being created has been exhausted. [EEXIST] Path2 already exists. [EFAULT] Path1 or path2 points outside the process's allocated address space. [EIO] An I/O error occurs while making the directory entry or allocating the inode. [EIO] An I/O error occurs while making the directory entry for path2, or allocating the inode for path2, or writing out the link contents of path2. [ELOOP] Too many symbolic links are encountered in translating the pathname. This is taken to be indicative of a looping symbolic link. [ENAMETOOLONG] A component of a pathname exceeds {NAME_MAX} characters, or an entire path name exceeds {PATH_MAX} characters. [ENOENT] A component of path2 does not name an existing file or path2 is an empty string. [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 there is no space left on the file system that will contain the sym- bolic link. [ENOSPC] There are no free inodes on the file system on which the symbolic link is being created. [ENOTDIR] A component of the path2 prefix is not a directory. [EROFS] The file path2 would reside on a read-only file system. SEE ALSO
ln(1), link(2), unlink(2), symlink(7) HISTORY
The symlink() function call appeared in 4.2BSD. 4.2 Berkeley Distribution June 4, 1993 4.2 Berkeley Distribution

Check Out this Related Man Page

symlink(2)							System Calls Manual							symlink(2)

NAME
symlink - make symbolic link to a file SYNOPSIS
DESCRIPTION
The function creates a symbolic link. Its name is the pathname pointed to by path2, which must be a pathname that does not name an existing file or symbolic link. The contents of the symbolic link are the string pointed to by path1. RETURN VALUE
Upon successful completion, returns 0. Otherwise, it returns -1 and sets to indicate the error. ERRORS
If fails, is set to one of the following values: [EACCES] Write permission is denied in the directory where the symbolic link is being created, or search permission is denied for a component of the path prefix of path2. [EEXIST] The path2 argument names an existing file or symbolic link. [EFAULT] path1 or path2 points outside the process's allocated address space. The reliable detection of this error is implementation-dependent. [EIO] An I/O error occurred while reading from path1, making the directory entry for path2, allocating the inode for path2, or writing out the link contents of path2. [ELOOP] Too many symbolic links were encountered in resolving path2. [ENAMETOOLONG] The length of the path2 argument exceeds or pathname resolution of a symbolic link produced an intermediate result that exceeds or a pathname component is longer than [ENOENT] A component of path2 does not name an existing file or path2 is an empty string. [ENOSPC] The directory in which the entry for the new symbolic link is being placed cannot be extended because no space is left on the file system containing the directory, or the new symbolic link cannot be created because no space is left on the file system which will contain the link, or the file system is out of file- allocation resources. [ENOTDIR] A component of the path prefix of path2 is not a directory. [EROFS] The new symbolic link would reside on a read-only file system. APPLICATION USAGE
Like a hard link, a symbolic link allows a file to have multiple logical names. The presence of a hard link guarantees the existence of a file, even after the original name has been removed. A symbolic link provides no such assurance; in fact, the file named by the path1 argu- ment need not exist when the link is created. A symbolic link can cross file system boundaries. Normal permission checks are made on each component of the symbolic link pathname during its resolution. AUTHOR
was developed by the University of California, Berkeley. SEE ALSO
cp(1), chown(2), link(2), lstat(2), open(2), readlink(2), unlink(2), symlink(4), <unistd.h>. STANDARDS CONFORMANCE
CHANGE HISTORY
First released in Issue 4, Version 2. symlink(2)

Featured Tech Videos