syslog level

LogLevel 日志级别

Description: Controls the verbosity of the ErrorLog Syntax: LogLevel level Default: LogLevel warn Context: server config, virtual host Status: Core Module: core LogLevel adjusts the verbosity of the messages recorded in the error logs (see ErrorLog directive). The following levels are available, in order of decreasing significance: Level Description Example emerg Emergencies - system is unusable. "Child cannot open lock file. Exiting" alert Action must be taken immediately. "getpwuid: couldn't determine user name from uid" crit Critical Conditions. "socket: Failed to get a socket, exiting child" error Error conditions. "Premature end of script headers" warn Warning conditions. "child process 1234 did not exit, sending another SIGHUP" notice Normal but significant condition. "httpd: caught SIGBUS, attempting to dump core in ..." info Informational. "Server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers)..." debug Debug-level messages "Opening config file ..." When a particular level is specified, messages from all other levels of higher significance will be reported as well. E.g., when LogLevel info is specified, then messages with log levels of notice and warn will also be posted. Using a level of at least crit is recommended. For example: LogLevel notice Note When logging to a regular file messages of the level notice cannot be suppressed and thus are always logged. However, this doesn't apply when logging is done using syslog. ----------------------- LogLevel 指令 说明: 控制错误日志的详细程度 语法: LogLevel 级别 默认值: LogLevel warn LogLevel用于调整记于错误日志中的信息的详细程度。(参阅ErrorLog指令)。可以选择下列级别，依照重要性降序排列： Level Description Example emerg   紧急 - 系统无法使用。  "Child cannot open lock file. Exiting" alert      必须立即采取措施。      "getpwuid: couldn't determine user name from uid" crit        致命情况。                     "socket: Failed to get a socket, exiting child" error     错误情况。                     "Premature end of script headers" warn     警告情况。                      "child process 1234 did not exit, sending another SIGHUP" notice   一般重要情况。               "httpd: caught SIGBUS, attempting to dump core in ..." info       普通信息。                      "Server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers)..." debug    出错级别信息                   Opening config file ..." 当指定了特定级别时，所有级别高于它的信息也会同时报告。比如说，当指定了LogLevel info时，所有 notice和warn级别的信息也会被记录。 建议至少要使用crit级别。     错误日志输入一些： http://www.wangchao.net.cn/bbsdetail_1475421.html   LogLevel crit 13718 [Mon Jan 25 13:57:15 2010] [notice] SIGUSR1 received.  Doing graceful restart 13719 [Mon Jan 25 13:57:15 2010] [notice] lighttpd/1.4.25 (Unix) mod_ssl/1.4.25 OpenSSL/0.9.8e-fips-rhel5 confi      gured -- resuming normal operations 13720 [Mon Jan 25 13:57:16 2010] [notice] child pid 15782 exit signal Segmentation fault (11) 13721 [Mon Jan 25 13:57:16 2010] [notice] child pid 15784 exit signal Segmentation fault (11) 13722 [Mon Jan 25 13:57:16 2010] [notice] child pid 15803 exit signal Segmentation fault (11) 13723 [Mon Jan 25 13:57:16 2010] [notice] child pid 15835 exit signal Segmentation fault (11)