Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rfio_msymlink(3) [debian man page]

RFIO_SYMLINK(3) 					      Rfio Library Functions						   RFIO_SYMLINK(3)

NAME
rfio_symlink - create a symbolic link to a file SYNOPSIS
#include <sys/types.h> #include "rfio_api.h" int rfio_symlink (const char *oldpath, const char *newpath); int rfio_msymlink (const char *oldpath, const char *newpath); int rfio_msymlink_reset (); int rfio_symend (); DESCRIPTION
rfio_symlink creates a symbolic link newpath which contains the string oldpath. newpath may point to a non existing file. If newpath exists already, it will not be overwritten. Write permission is required on newpath parent. rfio_msymlink is identical to rfio_symlink but keeps the connection open to the server unless there are more than MAXMCON connections already opened. This is useful when issuing a series of symlink calls. The last rfio_msymlink call should be followed by a call to rfio_symend. rfio_msymlink_reset is to be used when your program is forking. In such a case the permanent connections opened with rfio_msymlink become shared between the parent and the child. Use rfio_msymlink_reset to perform the necessary reset and close of the socket file descriptor in the parent or the child in order to be sure that only of them will receice an answer from the RFIO daemon. See NOTES section below. RETURN VALUE
This routine returns 0 if the operation was successful or -1 if the operation failed. In the latter case, serrno is set appropriately. NOTES
Multiple connections using rfio_msymlink are thread-safe but not process-wide, therefore a forked child can share file descriptors opened with rfio_msymlink by its parent. Use rfio_msymlink_reset in such case. Multiple connections behaviour is undefined if you work in a multi-threaded environment and with threads not created using the LCG's Cthread interface. ERRORS
ENOENT A component of newpath prefix does not exist or oldpath is a null pathname. ENOMEM Insufficient memory. EACCES Search permission is denied on a component of the newpath prefix or write permission on the newpath parent directory is denied. EFAULT oldpath or newpath is a NULL pointer. EEXIST newpath already exists. ENOTDIR A component of the newpath prefix is not a directory. ENAMETOOLONG The length of oldpath or newpath exceeds CA_MAXPATHLEN or the length of a path component exceeds CA_MAXNAMELEN. SENOSHOST Host unknown. SENOSSERV Service unknown. SECOMERR Communication error. SEOPNOTSUP Not supported on Windows. SEE ALSO
Castor_limits(4), rfio_readlink(3), rfio_unlink(3), Cthread(3) AUTHOR
LCG Grid Deployment Team LCG
$Date: 2005/03/31 13:13:03 $ RFIO_SYMLINK(3)

Check Out this Related Man Page

LINK(2) 						     Linux Programmer's Manual							   LINK(2)

NAME
link - make a new name for a file SYNOPSIS
#include <unistd.h> int link(const char *oldpath, const char *newpath); DESCRIPTION
link() creates a new link (also known as a hard link) to an existing file. If newpath exists it will not be overwritten. This new name may be used exactly as the old one for any operation; both names refer to the same file (and so have the same permissions and ownership) and it is impossible to tell which name was the "original". RETURN VALUE
On success, zero is returned. On error, -1 is returned, and errno is set appropriately. ERRORS
EACCES Write access to the directory containing newpath is denied, or search permission is denied for one of the directories in the path prefix of oldpath or newpath. (See also path_resolution(7).) EEXIST newpath already exists. EFAULT oldpath or newpath points outside your accessible address space. EIO An I/O error occurred. ELOOP Too many symbolic links were encountered in resolving oldpath or newpath. EMLINK The file referred to by oldpath already has the maximum number of links to it. ENAMETOOLONG oldpath or newpath was too long. ENOENT A directory component in oldpath or newpath does not exist or is a dangling symbolic link. ENOMEM Insufficient kernel memory was available. ENOSPC The device containing the file has no room for the new directory entry. ENOTDIR A component used as a directory in oldpath or newpath is not, in fact, a directory. EPERM oldpath is a directory. EPERM The file system containing oldpath and newpath does not support the creation of hard links. EROFS The file is on a read-only file system. EXDEV oldpath and newpath are not on the same mounted file system. (Linux permits a file system to be mounted at multiple points, but link() does not work across different mount points, even if the same file system is mounted on both.) CONFORMING TO
SVr4, 4.3BSD, POSIX.1-2001 (but see NOTES). NOTES
Hard links, as created by link(), cannot span file systems. Use symlink(2) if this is required. POSIX.1-2001 says that link() should dereference oldpath if it is a symbolic link. However, since kernel 2.0, Linux does not do so: if oldpath is a symbolic link, then newpath is created as a (hard) link to the same symbolic link file (i.e., newpath becomes a symbolic link to the same file that oldpath refers to). Some other implementations behave in the same manner as Linux. POSIX.1-2008 changes the speci- fication of link(), making it implementation-dependent whether or not oldpath is dereferenced if it is a symbolic link. For precise con- trol over the treatment of symbolic links when creating a link, see linkat(2). BUGS
On NFS file systems, the return code may be wrong in case the NFS server performs the link creation and dies before it can say so. Use stat(2) to find out if the link got created. SEE ALSO
ln(1), linkat(2), open(2), rename(2), stat(2), symlink(2), unlink(2), path_resolution(7), symlink(7) COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2008-08-21 LINK(2)
Man Page