Rainer Gerhards wrote:
Ummm... should have thought about this. NULs are treated special. This
is routed in the sysklogd code. Rsyslog uses standard C strings for the
most part. Standard C strings are terminated as soon as the first NUL is
detected. So we can not allow NULs to be part of the message. Thus, NUL
is always escaped, no matter what the control character escape sequences
is.
Can you provide us with a debug log (rsyslogd -d -n) showing a message
with #000 being processed?
attached, you will find the output.
cheers,
raoul bhatia
--
____________________________________________________________________
DI (FH) Raoul Bhatia M.Sc. email. [EMAIL PROTECTED]
Technischer Leiter
IPAX - Aloy Bhatia Hava OEG web. http://www.ipax.at
Barawitzkagasse 10/2/2/11 email. [EMAIL PROTECTED]
1190 Wien tel. +43 1 3670030
FN 277995t HG Wien fax. +43 1 3670030 15
____________________________________________________________________
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
