Comment 2 for bug 1639936

That would be pretty cool, honestly, Colin, I didn't even think you'd see this. I mistyped the heading apparently, because I was actually referring to the disk_stress_ng wrapper script.

But now that you bring it up, an exit code other than 1 would be awesome and much easier to trap (and certainly less functional overhead on the user end than wrappers that make decisions based on discovered architecture)