| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
Description
This options option checks and opens the ‘crontab’ "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’..
Example:
Notes:
- Alerts will be sent using the common alert script, see chapter Alerts management - Update/reinstall common alert script
- License expiration alert levels are explained here: Check for license expiration
- If the ‘crontab’ "
crontab" file does not exist, it is initialized with comments in order to facilitate settings like this:
...
More details on crontab at: http://en.wikipedia.org/wiki/Crontab (credits: wikipedia)
The ‘-nomail’ parameter makes the script to run and just check if the key license dongle 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.
It is mainly used if you're running on Red Hat Enterprise Linux 6; version 7 and Fedora are using systemd feature to alert in case of service abnormal termination
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. It runs by default every 1 minute so alerts will be sent in bulk mode rather than one alert per error detected.
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 “telnet localhost <port>”. If no one if is connected, it will connect to the console via the ‘screen’ ‘screen’ command and will record the console output
NoteNotes:
- 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.
- it is possible to disable this feature from the Connect to guest console menu.
Logs archiving utility
This utility will archive services log files and guests console log files .(if not managed by the emulator itself)
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
...