Completed find action check_md5
This commit is contained in:
@ -2,7 +2,7 @@
|
||||
.\" First parameter, NAME, should be all caps
|
||||
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
|
||||
.\" other parameters are allowed: see man(7), man(1)
|
||||
.TH XORRISO 1 "Aug 10, 2009"
|
||||
.TH XORRISO 1 "Aug 12, 2009"
|
||||
.\" Please adjust this date whenever revising the manpage.
|
||||
.\"
|
||||
.\" Some roff macros, for reference:
|
||||
@ -67,6 +67,8 @@ Can issue commands to mount older sessions on Linux or FreeBSD.
|
||||
.br
|
||||
Can check media for damages and copy readable blocks to disk.
|
||||
.br
|
||||
Can attach MD5 checksums to each data file and the whole session.
|
||||
.br
|
||||
Scans for optical drives, blanks re-useable optical media.
|
||||
.br
|
||||
Reads its instructions from command line arguments, dialog, and files.
|
||||
@ -756,7 +758,8 @@ each single data file. If enabled then MD5 checksums get loaded from the image
|
||||
if there are any. At image generation time they are computed for each file
|
||||
which gets its data written into the new session. The checksums of files which
|
||||
have their data in older sessions get copied into the new session.
|
||||
For now checksums can be exploited only via find action get_md5.
|
||||
Checksums can be exploited via options -check_md5, -check_md5_r, and via find
|
||||
actions get_md5, check_md5.
|
||||
.TP
|
||||
\fB\-rom_toc_scan\fR "on"|"off"[:"emul_on"|"emul_off"]
|
||||
Read-only drives do not tell the actual media type but show any media as
|
||||
@ -1315,6 +1318,9 @@ Matches files which have ACL or any xattr.
|
||||
\fB\-has_any_xattr\fR :
|
||||
Matches files which have any xattr other than ACL.
|
||||
.br
|
||||
\fB\-has_md5\fR :
|
||||
Matches data files which have MD5 checksums.
|
||||
.br
|
||||
\fB\-has_filter\fR :
|
||||
Matches files which are filtered by -set_filter.
|
||||
.br
|
||||
@ -1432,6 +1438,11 @@ namespace "isofs".
|
||||
.br
|
||||
\fBget_md5\fR prints eventual recorded MD5 sum together with file path.
|
||||
.br
|
||||
\fBcheck_md5\fR compares eventual recorded MD5 sum with the file content
|
||||
and reports if mismatch.
|
||||
.br
|
||||
E.g.: -find / -not -pending_data -exec check_md5 FAILURE --
|
||||
.br
|
||||
\fBsetfattr\fR sets or deletes xattr name value pairs.
|
||||
.br
|
||||
E.g.: -find / -has_xattr -exec setfattr --remove-all '' --
|
||||
@ -2621,6 +2632,21 @@ have an -indev and a loaded image. ":force" may be appended after the number.
|
||||
"use=sector_map" does not read any media but loads the file given by option
|
||||
sector_map= and processes this virtual outcome.
|
||||
.TP
|
||||
\fB\-check_md5\fR severity iso_rr_path [***]
|
||||
Compare the data content of the given files in the loaded image with their
|
||||
recorded MD5 checksums, if there are any. In case of any mismatch an event of
|
||||
the given severity is issued. It may then be handled by appropriate settings of
|
||||
options -abort_on or -return_with which both can cause non-zero exit values
|
||||
of the program run. Severity ALL suppresses that event.
|
||||
.br
|
||||
This option reports match and mismatch of data files to the result channel.
|
||||
Non-data files cause NOTE events. There will also be UPDATE events from
|
||||
data reading.
|
||||
.TP
|
||||
\fB\-check_md5_r\fR severity iso_rr_path [***]
|
||||
Like -check_md5 but checking all data files underneath the given paths.
|
||||
Only mismatching data files will be reported.
|
||||
.TP
|
||||
.B osirrox restore options:
|
||||
.PP
|
||||
Normally xorriso only writes to disk files which were given as stdio:
|
||||
@ -3532,6 +3558,9 @@ ACL and xattr
|
||||
.BR setfacl(1),
|
||||
.BR getfattr(1),
|
||||
.BR setfattr(1)
|
||||
.TP
|
||||
MD5 checksums
|
||||
.BR md5sum(1)
|
||||
.br
|
||||
.SH AUTHOR
|
||||
Thomas Schmitt <scdbackup@gmx.net>
|
||||
|
Reference in New Issue
Block a user