]>
Commit | Line | Data |
---|---|---|
2c5db955 CP |
1 | /* error.h: |
2 | * | |
3 | * Error flagging routines | |
4 | */ | |
5 | ||
9e920a41 | 6 | /* SEVERITY GUIDELINES: |
7 | * | |
8 | * ERR_STOP: Something so bad has happened that the whole service must | |
9 | * stop. Something like a malloc() error or similar magnitude | |
10 | * error. | |
11 | * | |
12 | * ERR_FATAL: Something so bad has happened that the module cannot usefully | |
13 | * function any more, but won't necessarily prevent other modules | |
14 | * from working. | |
15 | * | |
16 | * ERR_ERROR: Something is wrong, perhaps a data structure is inconsistent | |
17 | * or something similar has gone wrong internally. This might | |
18 | * indicate a larger problem but the module can continue working | |
19 | * for now. | |
20 | * | |
21 | * ERR_WARNING: Something slightly out of the ordinary has happened (e.g. | |
22 | * the IRCD sent a bogus message). The module can continue | |
23 | * working though without serious harm. | |
24 | * | |
25 | * ERR_INFO: Not an error condition. Something noteworthy has happened, | |
26 | * like a major module has started up. These will typically be | |
27 | * seen all the time on most setups so try not to be too spammy. | |
28 | * | |
29 | * ERR_DEBUG: Not an error condition. Something less significant has | |
30 | * happened which might be of interest if someone is attempting | |
31 | * to debug a problem. Nevertheless try not to be too spammy. | |
32 | */ | |
2c5db955 CP |
33 | |
34 | #define ERR_DEBUG 0 | |
35 | #define ERR_INFO 1 | |
36 | #define ERR_WARNING 2 | |
37 | #define ERR_ERROR 3 | |
38 | #define ERR_FATAL 4 | |
b71fee1d | 39 | #define ERR_STOP 5 |
2c5db955 CP |
40 | |
41 | void Error(char *source, int severity, char *reason, ... ); |