> -----Original Message-----
> From: [email protected] [mailto:rsyslog-
> [email protected]] On Behalf Of [email protected]
> Sent: Tuesday, February 01, 2011 7:04 AM
> To: rsyslog-users
> Subject: [rsyslog] notes on parser development with a couple of
> questions
> 
> the rsyslog git repository is configured to not allow you to check in
> Makefile.am but you must have a file by that name in your plugins/pm*
> directory
> 
>   question: should this be forced manually with git add -f filename? or
> is
> there some other way that this should be done.
> 

I guess you are mixing s/t up: Makefile and Makefile.in are not accepted, but
Makefile.am is (at least in my git and the central repository).

> 
> 
> the parser modules get hold of the string, _after_ it has been
> sanitized,
> so instead of tab characters you have #011 strings to work with.
> 
>   question: how can the parser module tell what options were used in
> receiving the log message? I am trying to write a snare log receiver
> module (which sends tab separated logs), how can I tell if tabs have
> been
> sanitized when I'm looking at the message?

You can turn the sanitizion off, and also pri parsing. Here are the settings:

http://git.adiscon.com/?p=rsyslog.git;a=blob;f=tools/pmrfc3164.c;h=38f556a2a3
9418fb5ddea3ffff41f55f448fe36c;hb=HEAD#l63

Return RS_RET_NO (actually anything else but OK), and that will not happen.

Rainer
> 
> David Lang
> _______________________________________________
> 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

Reply via email to