Description
This options opens the ‘crontab’ root file in order to schedule those recursive jobs with ‘vi’ editor or if installed, with the ‘nano’ editor, or, if possible, with the ‘gedit’ graphical editor (Windows notepad like) or ‘emacs’.
Notes:
- Alerts will be sent using the common alert script, see chapter Alerts management - Update/reinstall common alert script Edit common alert script XXXXXXXXXXXXXXX
- License expiration alert levels are explained here: Check for license expiration
- If the ‘crontab’ file does not exist, it is initialized with comments in order to facilitate settings like this:
|
Expiration check alert (charon_expchk)
Note the expiration check alert is displayed by default 7 days before expiration, 15 days in the default crontab settings.
This number of days can be changed using parameter 1 as number of days
Example for 21 days, running everyday at 08:00AM and 04:00PM (16:00):
|
More details on crontab at: http://en.wikipedia.org/wiki/Crontab
The ‘-nomail’ parameter makes the script to run and just check if the key can be read: if not or if a timeout reading is detected, the aksusbd drivers are restarted.
Monitor abnormal termination of the guests (charon_mongstop)
This job is active by default, it is recommended not to prevent it from running. It's goal is to send alerts if a guest has been stopped whereas it was not requested.
Log events (charon_logevent)
This job is active by default, it is recommended not to prevent it from running. It's goal is to scan for events in the guests active log files and send alerts based on alert level defined by the administrator.
Console autoconnect (charon_console_autoconnect)
This utility will check if the guest is running: if the console log is not defined in the configuration file (set OPA0 log=xxx), it will check no one is connected to the console via “telnet localhost <port>”. If no one if connected, it will connect to the console via the ‘screen’ command and will record the console output
Note: if you want to connect to the console, via Connect to guest console menu option, you will have the option to kill the active one and then connect interactively.
Logs archiving utility
This utility will archive services log files and guests console log files.
Default from the crontab entry is to keep files for 60 days and then zip older log files. Zipped files will be kept for 6 months