gfs_pio_open(3) [debian man page]
GFS_PIO_OPEN(3) GFS_PIO_OPEN(3) NAME
gfs_pio_open - open a file in the Gfarm file system SYNOPSIS
#include <gfarm/gfarm.h> gfarm_error_t gfs_pio_open (const char * gfarm_url, int flags, GFS_File * gfp); DESCRIPTION
gfs_pio_open() opens a file in the Gfarm file system specified by gfarm_url, and returns a GFS_File structure to the address pointed by gfp. gfarm_url is a path name in the Gfarm file system, or a Gfarm URL in the form of gfarm://metaserver:port/path/name. Values of flags are constructed by a bitwise-inclusive-OR of the following list. Exactly one of the first three values should be speci- fied: GFARM_FILE_RDONLY Open for reading only. GFARM_FILE_WRONLY Open for writing only. GFARM_FILE_RDWR Open for reading and writing. GFARM_FILE_TRUNC If the file already exist and is a regular file, it will be truncated to length 0 if the open mode allows writing. RETURN VALUES
GFARM_ERR_NO_ERROR The function terminated successfully. GFARM_ERR_IS_A_DIRECTORY gfarm_url refers to a directory. GFARM_ERR_IS_A_SYMBOLIC_LINK gfarm_url refers to a symbolic link. GFARM_ERR_OPERATION_NOT_PERMITTED gfarm_url refers to not a regular file. GFARM_ERR_NO_SUCH_OBJECT A component used as a directory in gfarm_url does not exist. GFARM_ERR_NOT_A_DIRECTORY A component used as a directory in gfarm_url is not, in fact, a directory. GFARM_ERR_PERMISSION_DENIED The requested access to the file is not allowed, or one of the directories in gfarm_url did not allow search (execute) permission. Or, the authentication to the metadata server fails. GFARM_ERR_NO_MEMORY Insufficient memory was available. GFARM_ERR_INVALID_ARGUMENT flags is not valid. GFARM_ERR_GFARM_URL_HOST_IS_MISSING gfarm_url does not include a metadata server. GFARM_ERR_GFARM_URL_PORT_IS_MISSING gfarm_url does not include a port number of the metadata server. GFARM_ERR_UNKNOWN_HOST The metadata server cannot be resolved. GFARM_ERR_TOO_MANY_OPEN_FILES The process opens too many files. GFARM_ERR_TOO_MANY_OPEN_FILES_IN_SYSTEM The system limit on the total number of open files has been reached. GFARM_ERR_NETWORK_IS_UNREACHABLE Network is unrechable. GFARM_ERR_OPERATION_TIMED_OUT Connetion timeout occurs. GFARM_ERR_PROTOCOL Protocol error occurs. GFARM_ERR_BROKEN_PIPE Connection to the metadata server is broken. GFARM_ERR_PROTOCOL_NOT_SUPPORTED Specified authentication protocol is not supported. GFARM_ERR_AUTHENTICATION User authentication failed when connecting to the metadata server. Others An error except the above occurred. The reason is shown by gfarm_error_string(3). SEE ALSO
gfs_pio_close(3), gfs_pio_create(3), gfs_pio_eof(3), gfs_pio_error(3), gfs_pio_flush(3), gfs_pio_getc(3), gfs_pio_getline(3), gfs_pio_open(3), gfs_pio_putc(3), gfs_pio_putline(3), gfs_pio_puts(3), gfs_pio_read(3), gfs_pio_seek(3), gfs_pio_ungetc(3), gfs_pio_write(3) Gfarm 27 June 2010 GFS_PIO_OPEN(3)
Check Out this Related Man Page
GFREG(1) GFREG(1) NAME
gfreg - register a Gfarm file, Gfarm file fragments, or a Gfarm directory SYNOPSIS
gfreg [ -p ] [ -h filesystem-node | -H hostfile | -D domainname ] [ -a architecture ] program ... gfarm-URL gfreg [ -i ] [ -h filesystem-node | -H hostfile | -D domainname ] localfile ... gfarm-URL gfreg -N total-num-of-fragments -I fragment-index [ -h filesystem-node | -H hostfile | -D domainname ] localfile ... gfarm-URL gfreg -r [ -h filesystem-node | -H hostfile | -D domainname ] [ -a architecture ] [ directory | program | localfile ] ... gfarm-URL DESCRIPTION
The first form copies and registers the program as a Gfarm file gfarm-URL in the Gfarm filesystem. When gfarm-URL is a directory, multiple programs can be specified. After the registration, the gfarm-URL can be specified as a program name of gfrun(1) and gfmpirun_p4(1). With- out the -p option, only executable file can be specified. With the -p option, non-executable file can be specified as well. Without the -a option or the -h option, architecture of the program is assumed to be the same architecture as the client host on that gfreg(1) is exe- cuted, which is obtained by the Gfarm metaserver. The second form registers one or more localfiles as a single Gfarm file. Without the -i option, only non-executable file can be specified as localfile. With the -i option, both excutable and non-executable file can be specified as localfile. The destination filesystem node will be automatically selected by CPU load average. With any one of -h, -H, -D options, filesystem node can be limited. The third form registers localfile as a file fragment of a Gfarm file. The total number of fragments and the fragment index are specified by the -N option and the -I option, respectively. When gfarm-URL is a directory, multiple localfiles can be specified. The destination filesystemnode will be automatically decided by CPU load average unless any one of -h, -H, -D options is explicitly specified. When the gfreg command of this form is executed on a filesystem node, the local filesystem node is always selected rather than a remote filesys- temnode. In this case, -h, -H, -D options help to store files dispersively. The fourth form registers the directory as a Gfarm directory gfarm-URL, the program or the localfile as a Gfarm file gfarm-URL. If direc- tory have some sub directories and/or files, they will be registered recursively. The non-executable file localfile will be registered as a file has one fragment. A non-executable file in the directory will be registered in the same way. When gfarm-URL already exists as a directory, multiple directories, programs, and localfiles can be specified and they will be registered in gfarm-URL. They can be mixed in parameteres, while other forms inhibit this manner. If gfarm-URL does not exist, one directory or one program, or one localfile can be specified and it will be registered as gfarm-URL. Refer to the first form's part above to specify filesystem node thatprogfarms and files will reside with the -a option or the -h option. OPTIONS
-f overwrites gfarm-URL even if it exits as a Gfarm file. -? displays a list of command options. Gfarm 05 April 2006 GFREG(1)