Comment 4 for bug 944051

For the record, we had a debate about this: some people say skipped chunks or tables should not be a non-zero exit, and others say it should. More people, including myself, think the latter, so we'll stay with the previous comment. My thinking is: zero exit should be a true, total "AOK"--everything worked as expected. People who commonly have skipped chunks may find this change to be a pita, as it does break backwards-compat a little, but a skipped chunk really is indication that something didn't work right, e.g. MySQL didn't us the index for a chunk, or the chunk was too large on the slave, etc. And since it's easy enough to isolate this exit status, people can still filter it out: "zero" exit == 0 || 32 || 96 (32 & 64).