Table of Contents
pbg_mv - move a partitioned BCG graph
] source[.pbg] target[.pbg]
which is a partitioned BCG graph
encoded in the PBG format, into target.pbg.
Both names source.pbg
must not designate the same file. If target.pbg
already exists, it is removed
first, as well as all the BCG fragments and log fragments referred to in
(these fragments being stored either on the local machine or
on remote machines); however, the grid configuration file referred to in
is not removed, as this file may be used by other PBG files than
After the successful execution of this command, source.pbg no
longer exists. However, the grid configuration file referred to in source.pbg
is neither removed, renamed, nor modified as this file can be used by other
PBG files than source.pbg.
The difference between pbg_mv and the UNIX command
mv is that pbg_mv does a "deep" move, whereas mv does a "shallow" move
(only source.pbg is renamed and only target.pbg is removed if it exists already,
but their associated fragments are kept unchanged).
Refer to the gcf
manual pages for details about the GCF and PBG formats.
Exit status is 0 if everything is alright, 1 otherwise.
early prototype was written by Jerome Fereyre and Hubert Garavel. The current
version was developed by Wendelin Serwe and Hubert Garavel (INRIA Rhone-Alpes).
- partitioned BCG graph (input)
- resulting partitioned
BCG graph (output)
The binary code of pbg_mv
is available in $CADP/bin.`arch`/pbg_mv.
information is available from the CADP Web page located at http://cadp.inria.fr
Directives for installation are given in files $CADP/INSTALLATION_*.
changes and improvements to this software are reported and commented in
was not designed to ensure atomic transactions.
If an error occurs while renaming certain fragments, pbg_mv
the move and try to restore all fragments already renamed. However, if target.pbg
already existed, its removal and the removal of its fragments cannot be
Please report other bugs to firstname.lastname@example.org
Table of Contents