控制日志的详细度
Level | Description | Example |
| Emergencies - system is unusable 紧急 - 系统无法使用 | Child cannot open lock file. Exiting |
| Action must be taken immediately 必须立即采取措施 | getpwuid: couldn't determine user name from uid |
| Critical Conditions 致命情况 | socket: Failed to get a socket, exiting child |
| Error conditions 错误情况 | Premature end of script headers |
| Warning conditions 警告情况 | child process 1234 did not exit, sending another SIGHUP |
| Normal but significant condition 一般重要情况 | httpd: caught SIGBUS, attempting to dump core in ..." |
| Informational 普通信息 | Server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers)..." |
| Debug-level messages 出错级别信息 | Opening config file ..." |
1 When a particular level is specified, messages from all other levels of higher significance will bereported as well. | 当指定了特定级别时,所有级别高于它的信息也会同时报告 | |
2 E.g.when LogLevel info is specified, then messages with log levels of notice and warn will also be posted | 比如说 当指定了LogLevel info时,所有 notice和warn级别的信息也会被记录 | |
3 Using a level of at least crit is recommended | 建议至少要使用crit级别 |
尊贵的董事大人
英文标题不为空时 视为本栏投稿
需要关键字 描述 英文标题