Opened at 2015-04-12T19:19:36Z
#1204 new defect
Fix the logging subsystem
| Reported by: | wilmer | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | BitlBee | Version: | 3.2.2 |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Public server |
| OS version/distro: |
Description
The logging subsystem was introduced together with daemon mode back in ... well, 2003 maybe? And not touched ever since, pretty much.
It needs some cleaning up or just complete removal. Either just switch to always using syslog, or update it to sanely choose between console logging (when in daemon mode but not forking) and syslogging (in other cases).
Problem right now is that most of the calls to log_message() appear to happen early on during startup, before log_init(), until which point all logs just go to log_null(). So we should see how early on this could be done instead.
BitlBee's poor logging is often getting in the way of debugging so it would be nice to fix that.
I'll see if I do this at some point.
