View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005546 | unreal | ircd | public | 2020-01-29 09:33 | 2021-11-01 10:40 |
| Reporter | syzop | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 6.0.0-beta1 | ||||
| Summary | 0005546: U6: Logging code cleanup | ||||
| Description | Our logging infrastructure is quite a mess. In particular: 1. Lack of appropriate logging classes, causing me (and others) to use LOG_ERROR pretty much everywhere. Have a look at general logging in various programs (non-IRC), list the various options and pros/cons. 2. At many places there are calls to send a message to ircops or snomasks and then a subsequent call to logging. It should be easier to do both at the same time, since now this creates laziness and one of the 2 is sometimes not done. sendto_realops_and_log was a first step, but there should probably be more... like for snomask messages + log, and ability to specify a log level/type/whatever (see point 1) | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-01-29 09:33 | syzop | New Issue | |
| 2020-01-29 09:34 | syzop | Summary | Logging code cleanup => U6: Logging code cleanup |
| 2021-11-01 10:39 | syzop | Assigned To | => syzop |
| 2021-11-01 10:39 | syzop | Status | new => resolved |
| 2021-11-01 10:39 | syzop | Resolution | open => fixed |
| 2021-11-01 10:39 | syzop | Fixed in Version | => 6.0.0-beta1 |
| 2021-11-01 10:39 | syzop | Note Added: 0022145 | |
| 2021-11-01 10:40 | syzop | View Status | private => public |
