The result will be 0 for a successfull verification or repair, and non zero otherwise.
The full list of exit values are:
0 = success
1 = repair is possible
2 = repair is not possible
3 = invalid command line arguments
4 = no good par2 files found
5 = repair failed
6 = file i/o error
7 = internal error
8 = out of memory
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It would be nice if I could run par2cmdline to verify and get back exactly one line of output for good or bad.
Using one -q isn't nearly quiet enough, and two -q's doesn't give a final status.
Now what would be really wonderful would be to take:
dir/s/b *.par2 | par2 v -q
And just get back a list of good/bad results with maybe a final 'everything is great' type message.
Just check the exit result from par2.
The result will be 0 for a successfull verification or repair, and non zero otherwise.
The full list of exit values are:
0 = success
1 = repair is possible
2 = repair is not possible
3 = invalid command line arguments
4 = no good par2 files found
5 = repair failed
6 = file i/o error
7 = internal error
8 = out of memory
That may work, but it requires wrapping a script around it, where I'd prefer to just have visual verification.
Thanks