--On Tuesday, March 08, 2005 15:44 -0500 Daniel Fisla <[EMAIL PROTECTED]> wrote:
I see your point, especially when not being in control of client software. You may be in a hard position.
I assume your did already some research into this so I won't give you the RTFM answer. :-)
Yes lots :( That's why I was like I *must* be missing something.
Adding in your logging code should not be that hard, well, it depends what kind of logging you'd like or need and if you could use some mature C/C++ logging API.
syslog is obviously preferred and likely what I'll use...Though the MySQL server may have a bit of framework in there, it obviously has something since it already puts out a very limited set of messages on startup. Just need to find where those happen and start from there :)
In the past I had to add logging to IMAP servers and connectors. The problem you will get into is, unless you manage MySQL AB to accept these patches for good into their product, you in essence will be forking their source and will have to re-apply your patches, and do full regression testing, for each MySQL upgrade/version.
Yes, I realise this all to well. We're forced to patch/modify various packages slightly for our operation. Up to and including Apache (the scoreboard/status page can't display VHosts/mod_vhost_alias hosts by default, so we patch that in)
Under such loads even the slightest memory leak or resource locking can really mess things up.
Yup, I'm a very competent coder and am very familiar with coding 'high end robust server level' applications. Or whatever you want to call them.
It's amazing how quickly bugs can turn up when you repeat things a million times an hour :)
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
