MySQL Bugs: #39650: Proxy does not warn when both log-file and log-use-syslog are used

Bug #39650	Proxy does not warn when both log-file and log-use-syslog are used
Submitted:	25 Sep 2008 13:10
Reporter:	Kay Roepke	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Proxy: Core	Severity:	S3 (Non-critical)
Version:	0.7.0	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	logging, proxy

Description:
When starting the proxy with both log-file and log-use-syslog some of the log output could go to syslog and some to the specified log file.

How to repeat:
specify both --log-file= and --log-use-syslog at startup
messages that occur before opening the log file are sent to syslog instead of the log file.
subsequently the proxy opens the log file and from then on messages are sent to a different log consumer, causing confusion and possibly a loss of information to debug an issue

Suggested fix:
warn when both options are specified and turn off syslog support in that case.

Examples of which messages can possibly diverted:
- syntax error in defaults file
- relative --basedir specified

Kay Roepke writes: 
We need to find out whether this problem still exists and write a test for it.