From: Stephen Morris Date: Thu, 18 Sep 2014 17:29:32 +0000 (+0100) Subject: [3591] Small edits of logging documentation during review. X-Git-Tag: rt3470_base~12^2~4 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2e1a21fb4c781dfb71ac89b91d24d464e4937d25;p=thirdparty%2Fkea.git [3591] Small edits of logging documentation during review. --- diff --git a/doc/guide/logging.xml b/doc/guide/logging.xml index 0a89e276a8..7e54f1e7c3 100644 --- a/doc/guide/logging.xml +++ b/doc/guide/logging.xml @@ -8,7 +8,7 @@ Logging
- Logging configuration + Logging Configuration @@ -397,7 +397,7 @@ TODO; there's a ticket to determine these levels, see #1074
- Example Logger configurations + Example Logger Configurations In this example we want to set the global logging to @@ -532,25 +532,32 @@ file be created.
- Environment variables and initial logging + Logging During Kea Startup - Logging configuration is specified in the configuration file. However, - there are several early initialization routines that are conducted even - before configuration file is read and applied. They also apply if - the new configuration does not configure any logging. + The logging configuration is specified in the configuration file. + However, when Kea starts, the file is not read until some way into the + initialization process. Prior to that, the logging settings are + set to default values, although it is possible to modify some + aspects of the settings by means of environment variables. Note + that in the absence of any logging configuration in the configuration + file, the settings of (possibly modified) default configuration will + persist while the program is running. + + + The following environment variables can be used to control the + behavio of logging during startup: - There are several environment variables that control logging - behavior in the early phase of the bring up. Once configuration that hold - logging configuration is parsed and applied they no longer apply. KEA_LOCKFILE_DIR Specifies a directory where logging system should create its - lock file. If not specified, it is ${prefix}/var/run/kea, where - prefix defaults to /usr/local. This variable must not end + lock file. If not specified, it is + prefix/var/run/kea, where + prefix defaults to /usr/local. + This variable must not end with a slash. There is one special value: "none", which instructs Kea to not create lock file at all. This may cause issues if several processes log to the same file. @@ -561,10 +568,33 @@ file be created. KEA_LOGGER_DESTINATION Specifies logging output. There are several special values. - "stdout" means standard output. "stderr" means standard error. - "syslog" means logging using syslog and a default name. - "syslog:foo" syntax is also permitted. It will log via syslog - using "foo" as a name. Any other value is treated as a name + + + stdout + + Log to standard output. + + + + stderr + + Log to standard error. + + + + syslog:fac + + Log via syslog. The optional + fac (which is + separated from the word "syslog" by a colon) + specifies the + facility to be used for the log messages. Unless + specified, messages will be logged using the + facility "local0". + + + + Any other value is treated as a name of the output file. If not specified otherwise, Kea will log to standard output.