PBG_MV manual page
Table of Contents

Name

pbg_mv - move a partitioned BCG graph

Synopsis

pbg_mv [ -i ] source[.pbg] target[.pbg]

Description

pbg_mv renames source.pbg, which is a partitioned BCG graph encoded in the PBG format, into target.pbg. Both names source.pbg and target.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 target.pbg (these fragments being stored either on the local machine or on remote machines); however, the grid configuration file referred to in target.pbg is not removed, as this file may be used by other PBG files than target.pbg.

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 and pbg manual pages for details about the GCF and PBG formats.

Exit Status

Exit status is 0 if everything is alright, 1 otherwise.

Authors

An early prototype was written by Jerome Fereyre and Hubert Garavel. The current version was developed by Wendelin Serwe and Hubert Garavel (INRIA Rhone-Alpes).

Operands

source.pbg
partitioned BCG graph (input)

target.pbg
resulting partitioned BCG graph (output)

Files

The binary code of pbg_mv is available in $CADP/bin.`arch`/pbg_mv.

See Also

bcg , gcf , pbg , bcg_merge , distributor , pbg_cp , pbg_info , pbg_open , pbg_rm

Additional information is available from the CADP Web page located at http://cadp.inria.fr

Directives for installation are given in files $CADP/INSTALLATION_*.

Recent changes and improvements to this software are reported and commented in file $CADP/HISTORY.

Bugs

pbg_mv was not designed to ensure atomic transactions. If an error occurs while renaming certain fragments, pbg_mv will abort 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 undone.

Please report other bugs to [email protected]

Table of Contents