My thoughts: This should be optional. Personally I don't want any more complexity in ommysql, as I'm trying to use this for relatively important production purposes.
Reasons: 1) I don't like configuration file dependencies. Especially since our DBA handles my.cnf and I handle rsyslog configuration, I think it's bad to have changes to an unrelated config file (my.cnf) effect another daemon (rsyslog). 2) The patch pre-configure options (TCP, cert validation, secure authentication) make no sense if MySQL is running on localhost. Honestly, I didn't even want a password for the MySQL user as needed in current ommysql. 3) Why is it assumed that something present in the global /etc/my.cnf is applicable to rsyslog? Just my two cents. -Jason Antman Rutgers University Rainer Gerhards wrote: > Hi all, > > I just received an interesting patch via the bug tracker: > > http://bugzilla.adiscon.com/show_bug.cgi?id=213 > > What I see looks good to me, but I am not really in into MySQL. Do you think > this is something I should merge? If not, why not? I'll wait until monday and > will merge if I have not heard any good argument against that. > > Thanks, > Rainer > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com > > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
