Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
monitor:loglevels [2019/12/19 00:08] – ↷ Links adapted because of a move operation digital manmonitor:loglevels [2023/01/23 14:00] (current) – LOG_CRIT *is* used in the current code digital man
Line 8: Line 8:
 | LOG_EMERG | System is Unstable | | (Not used in current code) | | | LOG_EMERG | System is Unstable | | (Not used in current code) | |
 | LOG_ALERT | action must be taken immediately | | (Not used in current code) | | | LOG_ALERT | action must be taken immediately | | (Not used in current code) | |
-| LOG_CRIT | Critical condtions | | (Not used in current code) | | +| LOG_CRIT | critical conditions Something very bad happened Out of memory, open file failures, socket creation errors, etc. The sysop is expected to need to take some action to restore functionality.  If the action is not obvious, they should ask for help. 
-| LOG_ERR | "error conditions| Something bad happened | Out of memory, file permission error, no such directory, corrupted message base etc. | The sysop is expected to need to take some action to restore functionality.  If the action is not obvious, they should ask for help. | +| LOG_ERR | error conditions | Something bad happened | File permission error, no such directory, corrupted message baseetc. | The sysop is expected to need to take some action to restore functionality.  If the action is not obvious, they should ask for help. | 
-| LOG_WARNING | warning conditions | Something wrong happened | Unexpected socket state, unable to create directory, failed password attempts, service disabled in INI file, etc. | Sysop should read the warning and may or may not take action.  The system is expected to be functional aside from the connection the warning is logged on. | +| LOG_WARNING | warning conditions | Something unexpected happened | Unexpected socket state, unable to create directory, failed password attempts, service disabled in INI file, etc. | Sysop should read the warning and may or may not take action.  The system is expected to be functional aside from the connection the warning is logged on. | 
-| LOG_NOTICE | normal but significant condition | Something somewhat unusual happened | Block IP address detected, too many mail recipients on an E-mail, File deleted or renamed, directory created, terminal connection terminated abnormally, ignored service is configured, etc | No action is expected.  This is normal behaviour, but something the Sysop should be able to find out about |+| LOG_NOTICE | normal but significant condition | Something somewhat unusual happened | Block IP address detected, too many mail recipients on an E-mail, File deleted or renamed, directory created, terminal connection terminated abnormally, ignored service is configured, etc | No action is expected.  This is normal behavior, but something the Sysop should be able to find out about |
 | LOG_INFO | informational | Something happened | Unknown user, file transferred, user connected, system started, etc. | No action expected.  Status update style messages | | LOG_INFO | informational | Something happened | Unknown user, file transferred, user connected, system started, etc. | No action expected.  Status update style messages |
 | LOG_DEBUG | debug-level messages | System is running | Send data to user, set up a JavaScript context, Various verbose messages. | No action expected.  Should be of interest to developers only.  May be useful for reporting a bug. | | LOG_DEBUG | debug-level messages | System is running | Send data to user, set up a JavaScript context, Various verbose messages. | No action expected.  Should be of interest to developers only.  May be useful for reporting a bug. |
monitor/loglevels.1576742936.txt · Last modified: 2019/12/19 00:08 by digital man
Back to top
CC Attribution 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0