gfreg - register a Gfarm file, Gfarm file fragments, or a Gfarm
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
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). Without
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 executed,
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 filesystemnode.
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 directory
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.
-f overwrites gfarm-URL even if it exits as a Gfarm file.
-? displays a list of command options.