[BlueOnyx:19690] Re: Updated CMU published

Michael Stauber mstauber at blueonyx.it
Fri Jun 10 15:23:45 -05 2016


Hi Richard,

> Just one thing to report is that pigz is causing one of our servers to
> almost grind to a halt.

Outch. That's bad. Yeah, "pigz" is a bit of a hog. As it uses all
available CPU cores you may even see that the process "pigz" uses more
than 100% CPU in "top". I've seen it soar to <800% CPU usage on a 15
core box.

> Is there an option available to preserve the previous behaviour?

Yeah. I put this into the code prior to release:

# Method of how to create TarBalls:
# internal: Archive::Tar
# external: tar system command
if (-e "/usr/bin/pigz") {
    $TARMETHOD = "external";
}
else {
    $TARMETHOD = "internal";
}

So the easiest way would be to rename /usr/bin/pigz to something else:

mv /usr/bin/pigz /usr/bin/pigz-disabled

If CMU doesn't find the pigz binary, then it will use the old method of
creating tarballs.

-- 
With best regards

Michael Stauber



More information about the Blueonyx mailing list