Open lkydev opened 6 years ago
On second thoughts, it is easy enough.
Exclude the influence of other files (test2.bin) by the following:
mkdir /some/dest
cp test1.bin.par2 /some/dest
cp test1.bin /some/dest
cd /some/dest
par2 verify test1.bin.par2
Inspect the output of verification and see if it reports OK.
Say there are two files in a directory:
I want to create par2 files for test1.bin, but suppose I make a mistake:
par2 create test1.bin.par2 test2.bin
Verification seems to be fine; command exit code is 0:
par2 verify test1.bin.par2 test1.bin
or even just
par2 verify test1.bin.par2
The only way to spot the error is to read the output closely. It says test2.bin was opened, not test1.bin.
Is there a better way to check that test1.bin is a wrong data file for the par2 file set?
Thanks.