Technical part
Scripts and files description
All scripts and files are located in the /opt/charon/utils folder except for .charon* files. The "Custom" column below indicates the file will not be overwritten with new kit installation/upgrade.
File | Type | Custom | Description |
charon_check.alertcmd | Shell script | Common script file used for alerts. If it does not exist, it is cloned from the example file (see below) | |
charon_check.alertcmd.example | Shell script | Example of common script file used for alerts. By default alerts are ‘wall’ and ‘mailx’ based | |
charon_check.mailfooter | Data file | Contains the mail footer used to send email alerts (see above) | |
charon_check.mailto | Data file | Contains the mail recipients list used to send email alerts (see above) | |
charon_common | Shell script | Script file including common variables and functions | |
charon_common_menu | Shell script | Script file including common variables and functions for menus | |
charon_console_autoconnect | Shell script | Script executed in the crontab file to connect to the guests console if no user is already connected, records all console output | |
charon_expchk | Shell script | License expiration check or key reading check with ‘-nomail’ parameter | |
charon_gstart | Shell script | Manages start/stop of the guests, defined as a service | |
charon_gstart.boot | Data file | Contains the guests list for start/stop: HW emulator and configuration file | |
charon_gstart.chkrun | Shell script | Optional script, user made, used to display status of the guest by the guest start menu (charon_menu_gstart) | |
charon_gstart.chkrun.example | Shell script | Example for the one one above | |
charon_gstart.stop | Shell script | Optional script that enables the customer to insert proper guests shutdown commands (based on ‘ssh’ or ‘expect’ tool for example). This script is generated on user request. | |
charon_gstart.stop.example | Shell script | Example for the script above including ‘ssh’ and ‘expect’ usage for VMS and Tru64 operating systems. | |
charon_linux_utils.kitXX.tar | Tar file | Contains the full Linux utils kit where XX represents the kit number. | |
charon_linux_utils.pdf | Document | This document file | |
charon_logarchive | Shell script | Manage services and guests console logs archiving | |
charon_logchk | Shell script | Manages guests log monitoring, defined as a service | |
charon_logchk.list | Data file | Contains the list of guests log files to monitor | |
charon_logevent | Shell script | Check for new events in the guests log files and sends alerts depending on the selected level | |
charon_menu_alertcmd | Shell script | Menu: alert script editing | |
charon_menu_alert.dat | Data file | Contains the options list for the alerts menu | |
charon_menu_c2v | Shell script | Menu: creates and send C2V file | |
charon_menu_console | Shell script | Menu: connection to guest console | |
charon_menu_cron | Shell script | Menu: edit crontab for license expiration check | |
charon_menudoc.dat | Data file | Contains the options list for the Documentation submenu | |
charon_menu_editcfg | Shell script | Menu: edit guests configuration file | |
charon_menu_gstart | Shell script | Menu: guests start/stop management, install service, edit guests list, etc… | |
charon_menu_hostinfo | Shell script | Menu: host information report management | |
charon_menuhostinfo.dat | Data file | Contains the options list for the Host information submenu | |
charon_menu_logchk | Shell script | Menu: guests log monitoring management | |
charon_menu_logevent | Shell script | Menu: selection for the of guests logs alert level | |
charon_menu_mailfooter | Shell script | Menu: customize alerts email footer | |
charon_menu_mailmode | Shell script | Menu: selection of the alert emails mode, HTML or pure TEXT | |
charon_menu_mailto | Shell script | Menu: mail recipients list management | |
charon_menumain.dat | Data file | Contains the options list for the main menu | |
charon_menu_sendlogs | Shell script | Menu: send configuration and log files via email | |
charon_menu_showlic | Shell script | Menu: show license content | |
charon_menu_walloff | Shell script | Menu: enable/disable alert wall messages | |
charon_mongstop | Shell script | Monitors abnormal termination of the services (guests) | |
charon_setup | Shell script | Charon installation/upgrade/remove script | |
charon_showhostinfo | Shell script | Gather Charon server information | |
events | Folder | Contains the events found in guests log files that will be sent via mail. Contains only events detected since last charon_logevent script execution (crontab) | |
fixgedit | Shell script | Prevents from gedit command to display garbage messages. Execute this script before like this: # . /opt/charon/utils/fixgedit | |
guest_shutdown.exp | Expect script | This ‘expect’ script contains sequence for Tru64 and VMS shutdown. See explanation in the Tricks and Tips chapter | |
kit.version | Data file | Contains kit version and release date (updated by the maketar script below) | |
Perl script | Menu display based on data file | ||
menusetup | Shell script | Kit installation script, setup the ‘menu’ command | |
Perl module | Contains enhanced display commands used by menu_mod.pl | ||
pluto.cfg.example | Data file | Configuration file used for guests tests | |
release-notes | Text file | Release notes | |
requests | Folder | Contains flag files that determines the guest has been stopped properly (requested stop). If the guest is stopped and the file does not exist, it indicates an abnormal termination of the guest Flag files are empty and have the following name: configuration file name + ".stop" (example: pluto.cfg.stop) | |
ssh-linux-openvms-setup.readme | Text file | Tips on how to create ssh trust between Linux and Openvms | |
ssh-linux-tru64-setup.readme | Text file | Tips on how to create ssh trust between Linux and Tru64 | |
templates | Folder | Contains templates used to send alerts via ‘mailx’ and ‘wall’ | |
$HOME/.charonconslogdir | Data file | Location for the console log file can be changed by placing the desired folder name in this file. Default is /opt/charon/log folder if this file is not created | |
$HOME/.charonkitfolder | Data file | Contains the Charon kit location provided at installation | |
$HOME/.charonlogevent | Data file | Contains the alert level selected for guests log files events | |
$HOME/.charonmailmode | Data file | Contains mail mode used to send email alerts, either HTML (default if the file does not exist) or TEXT. Used by charon_check.alertcmd script | |
$HOME/.charonsoftlicfolder | Data file | Contains the software license kit location (where the dinst and dunst script files are located) | |
$HOME/.charon.autoconnect | Data file | Console autoconnect enabled (contains 1) or disabled (contains 0) | |
$HOME/.charon.recipient | Data file | Contains the email recipient selected when sending hasp_srm_view output, C2V file or host information html report | |
$HOME/.charon.lastrecipient | Data file | Contains the last email recipient used for the above options in order to prevent from typing again the email address |
Notes:
Menu data files format is detailed using the following command:
# /opt/charon/utils/menu_mod.pl -fd
Manual services management
There are 2 services that can be installed:
- charon_gstart: guests start/stop
- charon_logchk: log monitoring
Request | Command |
Services list |
|
Prevent service to start at boot |
|
Enable service start at boot |
|
Start or Stop service |
Without supplemental parameter, all guests or logs monitoring are stopped To stop a dedicated guest, add the configuration file name To stop a dedicated log file monitoring, add the log file name Files can be truncated to their name only, directory and extension will be automatically completed Example:
|
Service status |
|
Remove service |
|
On Fedora Linux, it is recommended to add the parameter ‘-–skip-systemctl
’ when using the service command.
Example:
# service -–skip-systemctl charon_gstart stop pluto
© Stromasys, 1999-2024 - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.