log-level

The log-level command sets the system wide log-level or the log-level for a specific task or process. In addition, you can set the log type for a specific log level on a per-task basis.

Syntax

log-level <task-name | all> <log-level>

Arguments

<task-name>: Enter the name of the specific task for which you want to set. Use 'all' to set the log level for all tasks.

<log-level>: Select the log level either by name or by number:

  • emergency (1)
  • critical (2)
  • major (3)
  • minor (4)
  • warning (5)
  • notice (6)
  • info (7)
  • trace (8)
  • debug (9)
  • detail (10)

Note:

The log setting changes made by the log-level command do not persist after a reboot. Upon reboot, you must change the log settings in the system configuration for them to persist. When entering multiple log types in the log-type-list argument, use a space for separation.

By default the syslogd task log level is emergency; other settings cause high CPU usage. The log level resets to emergency whenever the configuration is saved and activated, and syslogd is not affected by the log-level all commands.

Exceptions

You cannot change the log level for the following tasks with the log-level command; it is set once when they are created at startup:
  • authqueue
  • fragHandler
  • heap
  • healthCheckd
  • SSHD
  • tLFMiBd
To set the log level for the preceding tasks, use system-log-level and process-log-level in system-config.

Note:

Although in most cases system-log-level and process-log-level are RTC-enabled, for the preceding tasks, you must reboot the system for the changes to take affect.

Example

ORACLE# log-level system warning