testps - Try out various PS modules on your system, and find one that works, optionally installing it.
The parts of CGIBurn that manipulate processes need a portable way to find out information about those processes. The closest thing to a portable way to do that is the UNIX ps(1) command, but different systems use different flags and print different output with their ps commands. A PS module knows what flags to use and what the output means.
testps tries out a PS module, and sees if it works. If it is asked to, it will scan all PS modules looking for one that works, and install it in the appropriate place.
By default, testps will display a list of processes, with child processes appearing below their parent and indented. If you are testing your own PS module, you can compare this to the output from your system's standard ps command to see if your module is working.
testps [-hqQ] [-d debug-level] [-L LIBLIB] [-si]
-q: Be quiet.
-Q: Be vewwy, vewwy quiet.
-h: Display help message
-d: Print debug messages at level debug-level
-L: Use LIBLIB as the cgi-lib/lib file, instead of getting it from
the configuration.
-s: Scan all PS modules, and don't stop until we find one that works.
Print an error message and exit with failure if no modules
work.
-i: Implies -s. When we find a working module, make a symlink to make
that the default PS module for this system.
smartinstall, ps(1), CGIBurn::Conf, CGIBurn::PS, CGIBurn::PS::Default, CGIBurn::JobControl.