RFIO_UNLINK

Section: Rfio Library Functions (3)
Updated: $Date: 2005/03/31 13:13:04 $
Index Return to Main Contents
 

NAME

rfio_unlink - remove a file entry  

SYNOPSIS

#include <sys/types.h>
#include "rfio_api.h"

int rfio_unlink (const char *path);
int rfio_munlink (const char *path);
int rfio_munlink_reset ();
int rfio_unend ();
 

DESCRIPTION

rfio_unlink removes a file entry.
path
specifies the logical pathname relative to the current directory or the full pathname.

rfio_munlink is identical to rfio_unlink 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 unlink calls. The last rfio_munlink call should be followed by a call to rfio_unend.

rfio_munlink_reset is to be used when your program is forking. In such a case the permanent connections opened with rfio_munlink become shared between the parent and the child. Use rfio_munlink_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.

rfio_munlink_reset is to be used when your program is forking. In such a case the permanent connections opened with rfio_munlink become shared between the parent and the child. Use rfio_munlink_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_munlink are thread-safe but not process-wide, therefore a forked child cann share file descriptors opened with rfio_munlink 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

EPERM
path is a directory.
ENOENT
The named file does not exist or is a null pathname.
EACCES
Search permission is denied on a component of the path prefix or write permission is denied on the parent directory or the parent has the sticky bit S_ISVTX set and

the effective user ID of the requestor does not match the owner ID of the file and

the effective user ID of the requestor does not match the owner ID of the directory and

the file is not writable by the requestor and

the requestor is not super-user.

EFAULT
path is a NULL pointer.
ENOTDIR
A component of path prefix is not a directory.
ENAMETOOLONG
The length of path exceeds CA_MAXPATHLEN or the length of a path component exceeds CA_MAXNAMELEN.
SENOSHOST
Host unknown.
SENOSSERV
Service unknown.
SECOMERR
Communication error.
 

SEE ALSO

Castor_limits(4), rfio_rmdir(3), Cthread(3)  

AUTHOR

LCG Grid Deployment Team