Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rfio_open(3) [debian man page]

RFIO_OPEN(3)						      Rfio Library Functions						      RFIO_OPEN(3)

NAME
rfio_open - opens a file SYNOPSIS
#include <sys/types.h> #include "rfio_api.h" int rfio_open (const char *path, int flags, int mode); Under Linux, for large files: #define _LARGEFILE64_SOURCE #include <sys/types.h> #include "rfio_api.h" int rfio_open64 (const char *path, int flags, int mode); For large files, under other systems: #include <sys/types.h> #include "rfio_api.h" int rfio_open64 (const char *path, int flags, int mode); DESCRIPTION
rfio_open opens the file whose name is the string pointed to by path, a character string containing the filename specification, and asso- ciates a FILE stream with it. flags are formed by ORing the following values: O_RDONLY Open for reading only O_WRONLY Open for writing only O_RDWR Open for reading and writing O_NDELAY Do not block on open O_APPEND Append on each write O_CREAT Create file if it does not exist O_TRUNC Truncate size to 0 O_EXCL Error if create and file exists O_LARGEFILE When size can be superior to 2GB-1. See NOTES mode specifies the permission bits to be set if the file is created. Opening a file with O_APPEND set causes each write on the file to be appended to the end. If O_TRUNC is specified and the file exists, the file is truncated to zero length. If O_EXCL is set with O_CREAT, then if the file already exists, the open returns an error. This can be used to implement a simple exclusive access locking mechanism. If O_EXCL is set and the last component of the pathname is a symbolic link, the open will succeed even if the symbolic link points to an existing name. If the O_NDELAY flag is specified and the open call would result in the process being blocked for some reason (for example waiting for a carrier on a dial-up line), the open returns immediately. The first time the process attempts to perform IO on the open file, it will block (not currently implemented). On systems that support the Large Files, O_LARGEFILE in rfio_open allows files whose sizes cannot be represented in 31 bits to be opened. RETURN VALUE
If successful, returns a non-negative integer which may be used to refer to the file on subsequent rfio_write, rfio_read and rfio_close calls. On failure, rfio_open returns -1 and the error code is stored in serrno. ERRORS
ENOENT The named file/directory does not exist or is a null pathname. EACCES Search permission is denied on a component of the path prefix. EBUSY Device or resource busy. Happens if you try to open in write mode a LCG file that is in an active migration stream. 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_write(3),rfio_read(3),rfio_close(3) NOTES
On Irix, Tru64 and IA64 the 64 bit mode is the default one, open and open64 are identical. The flag O_LARGEFILE is accepted on Irix and IA64 (where it has no effect) but not on Tru64. On all other platforms, rfio_open with O_LARGEFILE is equivalent to a call to rfio_open64. AUTHOR
LCG Grid Deployment Team LCG
$Date: 2005/03/31 13:13:03 $ RFIO_OPEN(3)

Check Out this Related Man Page

RFIO_STAT(3)						      Rfio Library Functions						      RFIO_STAT(3)

NAME
rfio_stat - get information about a file or directory SYNOPSIS
#include <sys/types.h> #include "rfio_api.h" int rfio_stat (const char *path, struct stat *statbuf); int rfio_fstat (int s, struct stat *statbuf); int rfio_lstat (const char *path, struct stat *statbuf); int rfio_mstat (const char *path, struct stat *statbuf); int rfio_mstat_reset (); int rfio_end (); Under Linux, for large files: #define _LARGEFILE64_SOURCE #include <sys/types.h> #include "rfio_api.h" int rfio_stat64 (const char *path, struct stat64 *statbuf); int rfio_fstat64 (int s, struct stat64 *statbuf); int rfio_lstat64 (const char *path, struct stat64 *statbuf); int rfio_mstat64 (const char *path, struct stat64 *statbuf); For large files, under other systems: #include <sys/types.h> #include "rfio_api.h" int rfio_stat64 (const char *path, struct stat64 *statbuf); int rfio_fstat64 (int s, struct stat64 *statbuf); int rfio_lstat64 (const char *path, struct stat64 *statbuf); int rfio_mstat64 (const char *path, struct stat64 *statbuf); DESCRIPTION
rfio_stat gets information about a file or directory. rfio_lstat is identical to rfio_stat except for symbolic links. In this case, the link itself is statted and not followed. rfio_fstat is identical to rfio_stat but works on the file descriptor s returned by rfio_open. rfio_mstat is identical to rfio_stat 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 stat calls. The last rfio_mstat call should be followed by a call to rfio_end. rfio_mstat_reset is to be used when your program is forking. In such a case the permanent connections opened with rfio_mstat become shared between the parent and the child. Use rfio_mstat_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. path specifies the logical pathname relative to the current directory or the full pathname. statbuf is a pointer to a stat structure, receiving result of your query. The 64 bits functions must be used for large files. They have the same syntax as the normal stat functions except that they use a stat64 structure. 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_mstat are thread-safe but not process-wide, therefore a forked child can share file descriptors opened with rfio_mstat by its parent. Use rfio_mstat_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 The named file/directory does not exist or is a null pathname. EBADF s is not a valid file descriptor. EACCES Search permission is denied on a component of the path prefix. EFAULT path or statbuf 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_chmod(3), rfio_chown(3), Cthread(3) AUTHOR
LCG Grid Deployment Team LCG
$Date: 2005/03/31 13:13:03 $ RFIO_STAT(3)
Man Page