nested/derived source statements?
Hello, Ie, I have source s_tcp6 { tcp6(log_fetch_limit(25) port(601)); } source s_tcp4 { tcp(log_fetch_limit(25) port(601)); }; and I would like to have another source s_tcp { s_tcp4; s_tcp6; }; but no matter what I try, I get syntax errors. Is it not possible to have nested/derived source statements? -Jan
No, you can only nest log and filter statements Sent: Monday, May 03, 2010 5:13:11 PM From: Jan Schaumann <jschauma@netmeister.org> To: syslog-ng@lists.balabit.hu Subject: [syslog-ng] nested/derived source statements?
Hello,
Ie, I have
source s_tcp6 { tcp6(log_fetch_limit(25) port(601)); }
source s_tcp4 { tcp(log_fetch_limit(25) port(601)); };
and I would like to have another
source s_tcp { s_tcp4; s_tcp6; };
but no matter what I try, I get syntax errors. Is it not possible to have nested/derived source statements?
-Jan
------------------------------------------------------------------------
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html
"Patrick H." <syslogng@feystorm.net> wrote:
No, you can only nest log and filter statements
Yay, feature request! :-) -Jan
I personally dont think this is needed. You can always specify multiple sources in a single log statement, and you can filter by items within a source by adding a tag. But just my own humble opinion. Sent: Wednesday, May 05, 2010 1:55:22 PM From: Jan Schaumann <jschauma@netmeister.org> To: syslog-ng@lists.balabit.hu Subject: Re: [syslog-ng] nested/derived source statements?
"Patrick H." <syslogng@feystorm.net> wrote:
No, you can only nest log and filter statements
Yay, feature request! :-)
-Jan
------------------------------------------------------------------------
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html
On Wed, 2010-05-05 at 14:46 -0600, Patrick H. wrote:
I personally dont think this is needed. You can always specify multiple sources in a single log statement, and you can filter by items within a source by adding a tag. But just my own humble opinion.
that's exactly how I responded in the bugzilla for the ticket. :) -- Bazsi
Balazs Scheidler <bazsi@balabit.hu> wrote:
On Wed, 2010-05-05 at 14:46 -0600, Patrick H. wrote:
I personally dont think this is needed. You can always specify multiple sources in a single log statement, and you can filter by items within a source by adding a tag. But just my own humble opinion.
that's exactly how I responded in the bugzilla for the ticket. :)
Ah, right, I had replied to that: | bugzilla@bugzilla.balabit.com wrote: | | > you can use multiple source references in a log statement, or with the | > latest tags() stuff, you can filter based on tags. | | Ah, I didn't know about tags. That might be a reasonable work-around, | but it still seems to me like that -- a work-around. | | > Do you have any other usecase? | | Not at the moment. only, bugzilla didn't like my mail: <bugzilla@bugzilla.balabit.com>: host bugzilla.balabit.com[195.70.41.85] said: 554 5.1.1 <bugzilla@bugzilla.balabit.com>: Recipient address rejected: undeliverable address: mail for bugzilla.balabit.com loops back to myself (in reply to RCPT TO command) Anyway, it seems counter-intuitive to me to be able to combine other things and not sources, but it's not a big blocker for me. -Jan
participants (3)
-
Balazs Scheidler
-
Jan Schaumann
-
Patrick H.