This happens because the compress commands called via exec are
using verbose output which can then exceed the max size for the
output buffer, resulting in a "Error: stdout maxBuffer exceeded."
error. The output is never exposed anywhere, so there's no point
in using verbose output for these commands.
mde
commented
8 years ago
This happens because the compress commands called via exec are using verbose output which can then exceed the max size for the output buffer, resulting in a "Error: stdout maxBuffer exceeded." error. The output is never exposed anywhere, so there's no point in using verbose output for these commands.