sharkcz / collectl

git mirror of collectl releases

With collectl now on github the documents are all self contained.
For a list of commits use git log
For example: Last 5 commits

[loberman@lobefedora collectl]$ git log | more
commit 471bc215ec366e960a1989c4da188b2493e24148
Author: Laurence Oberman <[e-mail]>
Date:   Tue Aug 1 16:23:27 2023 -0400

    Added md devices to disk parse

commit b888504cef6582ba5f0a269af5a46b19c996a66c
Author: Laurence Oberman <[e-mail]>
Date:   Tue May 30 14:37:21 2023 -0400

    Update README

commit b33c643b3e30e025bbd466e9dd7836b1e5046118
Author: Laurence Oberman <[e-mail]>
Date:   Tue May 30 14:36:42 2023 -0400

    Update README

commit 42cd088d775d3f927b6c9daabb22c0136a1e05a4
Author: Laurence Oberman <[e-mail]>
Date:   Mon May 1 17:24:30 2023 -0400

    Modified the INSTALL script to work with RHEL9+ that have no
    chkconfig

commit 802cd4123330d7ddbdc61d901dd07b9f8461e33f
Author: Laurence Oberman <[e-mail]>
Date:   Tue Feb 7 13:53:05 2023 -0500

    Updated version numbers

commit 067f8de362479b9ec414aa5d7d8aa0d6d6c87630
Author: Laurence Oberman <[e-mail]>
Date:   Tue Feb 7 13:46:19 2023 -0500

    Report from Martin Arlitt about missing Network interfaces so added those to
 formatit.ph

If you're real lazy, just run INSTALL and it will install collectl into the
same locations as the rpm.  It will install as /usr/bin/collectl and all the
other runtime components will be placed into /usr/share/collectl.  If you
really care where everything goes, read the script as it's pretty short.
There's also an UNINSTALL that will completely remove everything.

If you want to be more creative, you can either hack up the installation
script or use it as a guide to move things around to whereever you want them
keeping a couple of things in mind:
- collectl.conf is looked for first in /etc and then in its binary directory
- all ph files must be in the same directory as collectl itself OR /usr/share/collectl