Mark Atwood wrote:
> MySQL, and thus currently Drizzle, logs stuff to it's error log. "Stuff"
> being errors, warnings, and info messages. Inside the code, they
> ultimately get sent to stderr, which is directed to whatever file is
> specified by the "log-error" option. It's all in the MySQL documentation
> at http://dev.mysql.com/doc/refman/6.0/en/error-log.html
>
> I'm changing that in Drizzle, replacing the error logging stuff with a
> plugin interface.
>
> The first implementation will, just like the current builtin system,
> write to a file, or to stderr. I expect soon after, plugins that send
> the messages to syslog, as SNMP traps, and to a CSV table, will be written.
>
Totally agree with this. Wonderful.
I'd like to point out the unfortunately related task to this one:
there are _MANY_ places in the server where we print things to stdout
and/or stderr and do not use sql_print_{warning|info|error}. I've found
some of them when marking messages for gettext. (but of course, didn't
change them)
So as Mark finishes this task, someone else may want to go through and
find places where we are logging but aren't using the current logging
system to do it. (This also counts places where we have made wrappers
around the current logging system)
Monty
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : drizzle-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
