|
cptobackup − creates a time-stamped copy of files, dirs ... mvtobackup − moves to a time-stamped rename of files, dirs ... |
|
cptobackup [--backdir] files|dir [ ...files|dir... ] cptobackup [--help | --version] mvtobackup [--backdir] files|dir [ ...files|dir... ] mvtobackup [--help | --version] |
|
For each file or folder listed as argument, cptobackup performs a cp -a or mv to a time-stamped destination in the same location folder as the source, unless a .mvtobackup folder exists at the same level as the source. When a .mvtobackup folder is at the same level as some source, the time-stamped copy/move is targeted into it. This prevents visible pollution, though this may lead to not-very-visible disk-space consumption ... |
|
--backdir |
|
attempts to create a .mvtobackup folder in current directory, stops if it fails or continues regular behaviour described above. (pay attention that the folder-level of targets must be at the same level of an existing .mvtobackup folder, thus, targets in other directory than the current won’t end in ./.mvtobackup) |
|
--version |
|
reports cptobackup or mvtobackup version. |
|
--help |
|
reports short cptobackup’s or mvtobackup’s usage. |
|
all performed operations are duly output to state things clear. |
|
cptobackup or mvtobackup return 1 if any error occured, though they usually try to go to the end of argument list. they return 0 for success without any failure. |
|
(1)cp, (1)mv |
|
cptobackup and mvtobackup have been thoroughtly used for years, yet no valid bug reports were confimed. Please report them to bozomake@disjunkt.com |
|
Jean-Daniel Pauget (bozomake@disjunkt.com) |
|
$Id: cptobackup.1.in 581 2010-04-08 21:42:14Z jd $ |