This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients Carl.Crowder, r.david.murray, vinay.sajip
Date 2011-05-25.15:28:39
SpamBayes Score 0.000332942
Marked as misclassified No
Message-id <>
And it goes on to say:

"[...] but a syslog application MAY modify these characters upon reception.  For example, it might change them into an escape sequence (e.g., value 0 may be changed to "\0")"

Flume should not break if it receives NULs.  But there should be a way to prevent generating them, and Vinay has agreed with that.  Now we just need a patch :)  (he's probably working on one...)
Date User Action Args
2011-05-25 15:28:40r.david.murraysetrecipients: + r.david.murray, vinay.sajip, Carl.Crowder
2011-05-25 15:28:40r.david.murraysetmessageid: <>
2011-05-25 15:28:39r.david.murraylinkissue12168 messages
2011-05-25 15:28:39r.david.murraycreate