debug_level statement

Use the debug_level statement to specify the type and quantity of logging information to be written to the log file.

Parameters

n

Used to specify the debug level. All log messages are written to syslogd. The value of n represents a particular debug level or combination of debug levels according to the values shown in Table 1.

To log a combination of debug levels, add together the debug level numbers. If a debug level value is not specified, the default debug level is 7, which captures all ERROR, WARNING, and EVENT messages.

Table 1 lists the possible values:

Table 1. debug_level values

Debug level	Logging level	Description
0	None	No messages of any kind are sent to the logging file after initialization is complete.
1	ERROR	Error messages indicate that something requires attention. Messages at this level can be fatal (terminating) or can indicate that an important part of the automated domain name registration application is not working properly. This information is logged at the syslogd ERROR priority level.
2	WARNING	Warning messages indicate that an error has occurred, but it is not severe enough to warrant an ERROR level. Corrective action might be necessary because the automated domain name registration application might not be functioning as intended. This information is logged at the syslogd WARNING priority level.
4	EVENT	Event messages are logged for events that occur periodically, like operator commands, UNIX signals, timer pops, receipt of a network message, and so on. This information is logged at the syslogd NOTICE priority level.
8	INFO	Informational messages are sent to the logging file. These messages do not require corrective action. This information is logged at the syslogd INFO priority level.
16	MESSAGE	Messages about the detailed contents of message packets that are sent between the GWM (Advisor) and the automated domain name registration application. Use these messages to assist debugging automated domain name registration application communications. This information is logged at the syslogd DEBUG priority level.
32	COLLECTION	Collection messages concern the details of managing the data in the DNS zones. This information is logged at the syslogd DEBUG priority level.
64	DEBUG	Debug messages are intended for Development or Service and give detail that customers do not normally want. The intention of this level of message is to provide information that is useful in debugging code, logic, or timing errors. This information is logged at the syslogd DEBUG priority level.
128	TRACE	Trace messages are intended for Development or Service to track code processing (footprints). This information is logged at the syslogd DEBUG priority level.