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
OPEN(2) System Calls Manual OPEN(2) NAME
open - open a file for reading or writing, or create a new file SYNOPSIS
#include <sys/types.h> #include <fcntl.h> int open(const char *path, int flags [, mode_t mode]) DESCRIPTION
Open opens the file path for reading and/or writing, as specified by the flags argument and returns a descriptor for that file. The flags argument may indicate the file is to be created if it does not already exist (by specifying the O_CREAT flag), in which case the file is created with mode mode as described in chmod(2) and modified by the process' umask value (see umask(2)). Path is the address of a string of ASCII characters representing a path name, terminated by a null character. The flags specified are formed by or'ing the following values O_RDONLY open for reading only O_WRONLY open for writing only O_RDWR open for reading and writing O_NONBLOCK 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 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 fail even if the symbolic link points to a non-existent name. If the O_NONBLOCK flag is specified and the open call would result in the process being blocked for some reason, the open returns immediately. Upon successful completion a non-negative integer termed a file descriptor is returned. The file pointer used to mark the current position within the file is set to the beginning of the file. The new descriptor is set to remain open across execve system calls; see close(2). The system imposes a limit on the number of descriptors open simultaneously by one process. ERRORS
The named file is opened unless one or more of the following are true: [ENOTDIR] A component of the path prefix is not a directory. [ENAMETOOLONG] The path name exceeds PATH_MAX characters. [ENOENT] O_CREAT is not set and the named file does not exist. [ENOENT] A component of the path name that must exist does not exist. [EACCES] Search permission is denied for a component of the path prefix. [EACCES] The required permissions (for reading and/or writing) are denied for the named file. [EACCES] O_CREAT is specified, the file does not exist, and the directory in which it is to be created does not permit writing. [EACCES] A device to be opened for writing is physically write protected. [ELOOP] Too many symbolic links were encountered in translating the pathname. (Minix-vmd) [EISDIR] The named file is a directory, and the arguments specify it is to be opened for writing. [EROFS] The named file resides on a read-only file system, and the file is to be modified. [EMFILE] The system limit for open file descriptors per process has already been reached. [ENFILE] The system file table is full. [ENXIO] The named file is a character special or block special file, and the device associated with this special file does not exist. [ENOSPC] O_CREAT is specified, the file does not exist, and the directory in which the entry for the new file is being placed cannot be extended because there is no space left on the file system containing the directory. [ENOSPC] O_CREAT is specified, the file does not exist, and there are no free inodes on the file system on which the file is being created. [EIO] An I/O error occurred while making the directory entry or allocating the inode for O_CREAT. [EFAULT] Path points outside the process's allocated address space. [EEXIST] O_CREAT and O_EXCL were specified and the file exists. SEE ALSO
chmod(2), close(2), dup(2), fcntl(2), lseek(2), read(2), write(2), umask(2). 4th Berkeley Distribution May 14, 1986 OPEN(2)