9510a3ae1a
Use normal asserts in log.cc
...
The logger can't use the asserts that log messages as it introduces a
cyclical dependency on the logger itself.
2018-08-17 18:09:51 +03:00
19684deb69
MXS-2014 Init and finish properly
...
If any part of initalization fails, no resources are held.
At finalization, release all resources.
Also re-implement recent changes made to log_manager.cc that
did not automatically move over to log.cc.
2018-08-16 11:09:30 +03:00
a586aa13c4
MXS-2014 Add proper OOM support
...
Not that I think it ever will be needed...
2018-08-16 09:59:43 +03:00
85b68c439a
MXS-2014 Still more cleanup of maxbase/log.h
2018-08-16 09:59:43 +03:00
8ae2997c4e
MXS-2014 Remove separate log_write() function
2018-08-16 09:59:43 +03:00
5b46d815e4
MXS-2014 Move message status checking into MessageRegistry
2018-08-16 09:59:43 +03:00
79b292dc39
MXS-2014 Additional cleanup of log.cc
2018-08-16 09:59:43 +03:00
5b70c7605c
MXS-2014 Some cleanup of log.cc
...
Unused stuff removed and unit variables collected into this_unit
structure.
2018-08-16 09:59:43 +03:00
0c479b5d13
MXS-2014 Enable asserts in log.cc
2018-08-16 09:59:43 +03:00
52e6e10e28
MXS-2014 Remove duplicate function
...
Two functions that essentially did the same thing, but had
slightly different name.
2018-08-16 09:58:00 +03:00
a191ed85a2
MXS-2014 Expose everything needed by the MaxScale log manager
2018-08-16 09:58:00 +03:00
1a6eb8165a
MXS-2014 Add log.[h|cc] to maxbase
...
Almost a verbatim copy of log_manager.[h|cc] with mxs changed
to mxb. The changes allow the MaxScale log manager to be moved
on top of this implementation.
2018-08-16 09:58:00 +03:00
