summain(1) [debian man page]
SUMMAIN(1) General Commands Manual SUMMAIN(1) NAME
summain - gather file checksums and metadata SYNOPSIS
summain [-c=CHECKSUM] [--checksum=CHECKSUM] [--config=FILE] [--dump-config] [--dump-memory-profile=METHOD] [--dump-setting-names] [--exclude=FIELD] [--generate-manpage=TEMPLATE] [-h] [--help] [--list-config-files] [--log=FILE] [--log-keep=N] [--log-level=LEVEL] [--log-max=SIZE] [--log-mode=MODE] [-m] [--mangle-paths] [--no-default-configs] [--output=FILE] [-f=OUTPUT-FORMAT] [--output-format=OUTPUT-FORMAT] [-r] [--relative-paths] [--secret=SECRET] [--version] [FILE]... DESCRIPTION
summain gathers metadata about files, and computes their checksums. It is intended to create a manifest of the files. The manifest can be used to see if something has changed: a new manifest can be created and compared with the old one with diff(1). The manifest looks like this: Name: foo/bar/foobar SHA1: 1234123413241324 Mtime: 2010-01-01 02:08:00.127651 +0000 Mode: 1755 The filename is URL-encoded to ensure it is purely ASCII. Mode is in octal. Only some inode fields are included. It does not make sense to compare, for example, the access time, so that is not included. Time stamps are given using microsecond precision, for the benefit of those filesystems that can support precise timestamps. (Should be nanosecond, but Python return timestamps as floating point, and nanosecond precision is too much for the floating point type.) The inode and device number fields will not be reported accurately. Instead, they are normalized so that manifests are useful after the files have been restored from backups. Accurate numbers would mean everything seems to have changed. Normalized means that there will be no differences. The numbers are reported so that hard links can be checked. Directories named on the command line will be recursed automatically. OPTIONS
-c, --checksum=CHECKSUM which checksums to compute: MD5, SHA1, SHA224, SHA256, SHA384, SHA512; use once per checksum type (default is SHA1) --config=FILE add FILE to config files --dump-config write out the entire current configuration --dump-memory-profile=METHOD make memory profiling dumps using METHOD, which is one of: none, simple, meliae, or heapy (default: simple) --dump-setting-names write out all names of settings and quit --exclude=FIELD do not output or compute FIELD --generate-manpage=TEMPLATE fill in manual page TEMPLATE -h, --help show this help message and exit --list-config-files list all possible config files --log=FILE write log entries to FILE (default is to not write log files at all); use "syslog" to log to system log, or "none" to disable log- ging --log-keep=N keep last N logs (10) --log-level=LEVEL log at LEVEL, one of debug, info, warning, error, critical, fatal (default: debug) --log-max=SIZE rotate logs larger than SIZE, zero for never (default: 0) --log-mode=MODE set permissions of new log files to MODE (octal; default 0600) -m, --mangle-paths mangle (obfuscate) paths --no-default-configs clear list of configuration files to read --output=FILE write output to FILE, instead of standard output -f, --output-format=OUTPUT-FORMAT choose output format (rfc822, csv, json) -r, --relative-paths print paths relative to arguments --secret=SECRET use SECRET to make mangled paths unguessable --version show program's version number and exit SUMMAIN(1)
Check Out this Related Man Page
GENBACKUPDATA(1) General Commands Manual GENBACKUPDATA(1) NAME
genbackupdata - generate backup test data SYNOPSIS
genbackupdata [--chunk-size=SIZE] [--config=FILE] [-c=SIZE] [--create=SIZE] [--depth=DEPTH] [--dump-config] [--dump-setting-names] [--file-size=SIZE] [--generate-manpage=TEMPLATE] [-h] [--help] [--list-config-files] [--log=FILE] [--log-keep=N] [--log-level=LEVEL] [--log-max=SIZE] [--max-files=MAX-FILES] [--no-default-configs] [--output=FILE] [--quiet] [--seed=SEED] [--version] DESCRIPTION
genbackupdata generates test data sets for performance testing of backup software. It creates a directory tree filled with files of dif- ferent sizes. The total size and the distribution of sizes between small and big are configurable. The program can also modify an exist- ing directory tree by creating new files, and deleting, renaming, or modifying existing files. This can be used to generate test data for successive generations of backups. The program is deterministic: with a given set of parameters (and a given pre-existing directory tree), it always creates the same output. This way, it is possible to reproduce backup tests exactly, without having to distribute the potentially very large test sets. The data set consists of plain files and directories. Files are either small text files or big binary files. Text files contain the "lorem ipsum" stanza, binary files contain randomly generated byte streams. The percentage of file data that is small text or big binary files can be set, as can the sizes of the respective file types. Files and directories are named "fileXXXX" or "dirXXXX", where "XXXX" is a successive integer, separate successions for files and directo- ries. There is an upper limit to how many files a directory may contain. After the file limit is reached, a new sub-directory is created. The first set of files go into the root directory of the test set. You have to give one of the options --create, --delete, --rename, or --modify for the program to do anything. You can, however, give more than one of them, if DIR already exists. (Giving the same option more than once means that only the last instance is counted.) (DIR) is created if it doesn't exist already. OPTIONS
--chunk-size=SIZE generate data in chunks of this size (default: 16384) --config=FILE add FILE to config files -c, --create=SIZE how much data to create (default: 0) --depth=DEPTH depth of directory tree (default: 3) --dump-config write out the entire current configuration --dump-setting-names write out all names of settings and quit --file-size=SIZE size of one file (default: 16384) --generate-manpage=TEMPLATE fill in manual page TEMPLATE -h, --help show this help message and exit --list-config-files list all possible config files --log=FILE write log entries to FILE --log-keep=N keep last N logs (10) --log-level=LEVEL log at LEVEL, one of debug, info, warning, error, critical, fatal (default: debug) --log-max=SIZE rotate logs larger than SIZE, zero for never (default: 0) --max-files=MAX-FILES max files/dirs per dir (default: 128) --no-default-configs clear list of configuration files to read --output=FILE write output to FILE, instead of standard output --quiet do not report progress --seed=SEED seed for random number generator (default: 0) --version show program's version number and exit EXAMPLES
Create data for the first generation of a backup: genbackupdata --create=10G testdir Modify an existing set of backup data to create a new generation: genbackupdata -c 5% -d 2% -m 5% -r 0.5% testdir The above command can be run for each new generation. GENBACKUPDATA(1)