Charon Report Utility V1.47 for Linux

Updates:

Bug solved when user was asked twice to specify the .cfg file (bug introduced in V1.46 and multi-products support)
NUMA balancing chapter reworked. Now generates an error alert if set to ON and Charon-PAR is installed
Added timedatectl output in all cases in 'Time service settings' chapter
'at' package is now required only if aksusbd is installed (HASP license) and if 'at' is installed a check if performed to verify 'atd' service is running
Charon-PAR: bug solved / always looking for log file in 'logs' subfolder if Toolkit is not used
Charon-PAR: if log file is not found in the same folder as the .cfg file, the log file is searched in .cfg file 'log.name' parameter and if not found, search default one with 'find' command, not NFS mounted, most recent. As this is not 100% sure the correct log file will be found, please specify log file name in .cfg file if Toolkit is not used
Added '-r' or '--reset' option to reset already known emulators list (useful in case of migration from non Toolkit to Toolkit emulators management)
Added support for AXP/VAX baremetal version (Charon Manager)
Reworked checks on several (systemd) services
HTML report: headings color change (not the same as navigation bar) for ease of reading
Minor display issue solved in crontab checks
Submenu added for 'Charon Toolkit', 'HASP license settings' and 'VE license settings' if installed
Reworked Charon virtual machines discovery: Charon Manager -> Toolkit -> Running processes (Note: discovery can be turned off using '-x' or '--nodiscovery' option)
Charon-SSP virtual machines: if power scheme is not set to Performance, a warning message is generated (recommended mode)
Inside the CharonReport zip file, emulators child folders have a 3 digit number in their name to avoid overwriting (before folders were based on .cfg file name so duplicates were possible)

Notes:

Multi Charon products on the same server environments are now supported.
The new emulators discovery system will first look for virtual machines (emulators) defined in the Charon Manager then in the Linux Toolkit if installed and then will look at running processes for running emulators that have not been discovered earlier. Once the discovery process is complete, the user can still add manually configuration files if not listed.
The emulators discovery system will try to find the related log files if the full path is not specified. We however strongly recommend full path to always been specified for emulators log files defined out of Charon Manager or the Linux Toolkit.
Run the script with ‘-h' or '--help’ for description and available parameters