2016-12-07 9:11 GMT+01:00 David Lang <[email protected]>: > On Wed, 7 Dec 2016, [email protected] wrote: > >>> when troubleshooting things like this, create a rule file that is as >>> minimal as you can get and parse with the -v option, it will show you what >>> it's doing as it walks through the line. >> >> Ok :) >> >>> >>> In this case, I seem to remember that number is defined as being followed >>> by a space, so you can't use it if the number is followed by a newline. >> >> I'll have to confirm that...but may I know why? Should I fill an issue if >> it's indeed that way? > > > I think it's a problem, several of the types require a space at the end, and > I think they should all be modified to allow either a space or a > end-of-line.
ack. It's on my list for early next year. > > I don't remember if I've opened an issue for this or not. > >>> there is the alternative capability in the v2 language, or define >>> multiple rules >> >> Multiple rules is what I'm trying now. I have tested alternate and I'm not >> able to get it working. >> Does alternative work for both...? >> >> * A or B (doc states it does) >> * A or nothing (that was my real question) > > > I'm not sure if you can have a blank item on one branch or not. If not, can > you have the branches both include a required item? (either the one before > or the one after) I *think* (but do not know for sure) this might work. Else I'll add early next year as well. Conceptionally, it really is alternative with a void branch. Raienr _______________________________________________ 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.
