-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 21 Jan 2010 01:49:47 +0100 Marc Schiffbauer <[email protected]> wrote:
> Am Mittwoch, 20. Januar 2010 19:20:31 schrieb Jakob Haufe: > > * Drop the message and report that we did so. That would be rather easy, > > but might not be what people want. > > > > But this might be the best option I guess. Maybe the original message could > then be written to a special logfile on disk. And then you have to check every now and then whether something ended up there? That's not nice, and rather complex to implement as well (file name should be configurable, maybe size limited, rotated, whatever) > > For me, this sums up to one question: > > > > Can we make ompgsql UTF/UCS-clean and at the same time not choke on > > non-UTF8 strings? Everyone is trying to be UTF-8 clean these days, so it > > would be bad if ompgsql could not keep up. > > I think this is a special case because rsyslog is not the originator of > those messages. It "just" transports them. And because the syslog-Protocol > does not define something like encoding in any way the best thing to do is > just leave those strings "as-is" and make the database behind it do so as > well with SQL_ASCII. I like the idea of seeing rsyslog as some kind of transport only. This is the best argument for switching to SQL_ASCII altogether so far. Rainer, do you have any thoughts on this? > I thing everythign else will be error prone in some way. The Documentation > of rsyslog should bring a big fat NOTE that the database must be SQL_ASCII > as other wise thesrings might not be accepted. Yes, and the createDB.sql for ompgsql should be changed as well. Regards, Jakob Haufe (sur5r) - -- ceterum censeo microsoftem esse delendam. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAktYxoIACgkQ1YAhDic+adZvugCffdUcjqR/EiQIGojSgEh8A8lU m2EAn1AZ1ebx4l+GCFqQLSvg6FqBZFvG =1POP -----END PGP SIGNATURE----- _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
