So there are some valid problems raised here. To give some background,
the problem that is being addressed is that changes to logging
configuration are non-atomic, basically meaning that it is common to get
duplicate or missing log messages when switching between log files; also
having two log files is kind of silly.
The perfect solution would have the following characteristics:
1) Only one log file from startup to shutdown
2) Only one place to configure logging (i.e. the logging subsystem)
3) Logging changes are atomic
This solution exhibits #1 & #2 (but only if the logging config or the
server environment hasn't changed significantly between shutdown and
startup) but not #3 (still impossible with the current code base). The
existing code does not meet any of these three characteristics.
--
- DML