Chapter 4: System Logging
NOTE
NTP logs are not included in the periodic log rotations. They accumulate in one
continuous file over a long period of time (
ntp.log
). Events are infrequent enough that the
NTP log file is unlikely to fill the entire log directory.
To change the frequency of log rotation:
Use
syslog period
(see
). You can configure the logs to rotate daily, weekly, or
monthly.
lunash:>
syslog period
<syslogperiod>
lunash:>syslog period daily
Log period set to daily.
Command Result : 0 (Success)
To change the number of rotated log files saved on the appliance:
Use
syslog rotations
(see
). You can save up to 100 rotated log files on the
appliance. This command allows you to define how long to keep old logs on the appliance (maximum: 100 logs,
rotated monthly).
lunash:>
syslog rotations
<#_of_rotations>
lunash:> syslog rotations 5
Log rotations set to 5.
Command Result : 0 (Success)
To manually rotate the current log file:
Use
syslog rotate
(see
). This command ensures that the most recent logs are
included when exporting them off the appliance.
lunash:>
syslog rotate
lunash:>syslog rotate
Command Result : 0 (Success)
Customizing Severity Levels
You can customize the logs stored on the appliance by setting the log severity level (see
for a description of the different levels). If you are concerned about the log directory filling
up, you can configure the appliance to store only the most severe events (
emergency
) and send the rest of
the logs to a remote syslog server (see
"Remote System Logging" on page 51
).
SafeNet Luna Network HSM 7.3 Appliance Administration Guide
007-013576-005 Rev. A 13 December 2019 Copyright 2001-2019 Thales
48
