As for me, most problems can be solved using existing template engine in
scripts. For example:
Template(name="sub" type="string" string="%timegenerated:::subseconds%")
set $.m = template("sub");
This could be much simpler than introducing a new type and a bunch of
accompaniyng functions.
--
Pavel Levshin
24.10.2013 19:44, Rainer Gerhards:
Finally at least some word about this:
The root problem is that script does not yet support a real datetime type.
So we get this as a string. With themplates, there are modifiers available
to specifiy the format (high/low precision). With script, no such thing
exists, and the core falls back to default which for historical reasons is
low precision.
The obvious solution is to enhance script engine & support infrastructure
to support datetime types. I've put this on the todo list, but I didn't get
a very high spot, I have to admit.
But at last you now know cause and reason.
Rainer
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
