Use_nslog Option

From Messaging Server Technical Reference Wiki
Jump to: navigation, search


Updated in release: 8.0


The use_nslog option (available under dispatcher, job_controller) may be set to 1 to enable use of nslog() for debugging output. This then enables the use of the logfile options, component.logfile.option-name, (or logfile.component.* in legacy configuration) for controlling logfile creation and rollover. Note that loglevel is not supported for the dispatcher and job_controller as their logging level is still controlled by use of their respective debug options. use_nslog defaults to 0 for the dispatcher and job_controller and 1 for the MMP.


The default value is: 0

Use with the MMP

DEPRECATED for the MMP and its components as of MS 8.0: The use_nslog option (available at levels including mmp, imapproxy, and popproxy) may be set to 1 to enable use of nslog() for debugging output. This then enables the use of the logfile options, component.logfile.option-name, (or logfile.component.* in legacy configuration) for controlling logfile creation and rollover.


The default value in this context is: 1


See also:

Use with the IMAP proxy

The default value in this context is: 1

Use with the POP proxy

The default value in this context is: 1

Use with dispatcher

The use_nslog Dispatcher option may be set to 1 to enable use of nslog() for Dispatcher debug log files. The default is 0. When use_nslog has been enabled, see also the logfile options that may be set as dispatcher.logfile.*. Note that the loglevel option is not supported for the Dispatcher as its debug level is controlled instead by use of the debug Dispatcher option, dispatcher.debug.


The default value in this context is: 0


See also:

Use with job controller

The use_nslog Job Controller option may be set to 1 to enable use of nslog() for Job Controller debug log files. The default is 0. When use_nslog has been enabled, see also the logfile options that may be set as job_controller.logfile.*. Note that the loglevel option is not supported for the Job Controller as its debug level is controlled instead by use of the debug Job Controller option, job_controller.debug.


The default value in this context is: 0


See also:


See also: