Table of Contents

Description

Use this option to check and open the root's "crontab" file in order to schedule recursive jobs.

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: License expiration check
  
• If the "crontab" file does not exist, it is initialized with comments in order to facilitate settings like this:

Expiration check alert (charon_expchk)

The expiration check alert sends alerts by default 15 days before expiration (7 days in interactive mode).

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 (credits: wikipedia)

The ‘-nomail’ parameter can be used to make the script check if the license dongle can be read: if not or if a timeout is detected, the aksusbd drivers are restarted. This is mainly used for debugging.

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 used only with Red Hat Enterprise Linux 6.x.

Red Hat Enterprise Linux 7.x and CentOS 7.x are using systemd feature to monitor service abnormal termination so the corresponding lines will not be added in the crontab.

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. The interval can be updated at your convenience.

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