Thank you very much, Mr. Arlt, for your prompt response! This seems to work just fine. I have another question. It would seem to me that the method I outlined *should* work, although the shorthand is preferable. Even so, it doesn't work. I seem to have trouble calling other filters. For example, syslog-ng doesn't yield a parse error if I use a filter identifier which doesn't exist (e.g. a typo). Also, it doesn't seem to evaluate the filter properly. The example copied below fails to catch any messages at all. Why is this? Am I misunderstanding the semantics of calling other filters or using connective operators? Again, thank you! On Fri, Dec 29, 2000 at 10:56:42AM -0700, Brad Arlt wrote:
On Fri, Dec 29, 2000 at 11:25:08AM -0600, Jon Marks wrote:
filter f_info { level(info) or level(notice) or .. or level(emerg); }; filter f_daemon { facility(daemon) and filter(f_info); };
This should condense into:
filter f_filtername { facility(daemon) and level(emerg..info); };
---------------------------------------------------------------------------- __o Bradley Arlt Email: arlt@cpsc.ucalgary.ca o__ _ \<_ WWW: www.acs.ucalgary.ca/~bdarlt _>/ _ (_)/(_) -Eat well, sleep peacefully, drink lots, and ride like hell. (_)\(_)
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng
-- Jonathan Marks Systems Administrator, Production Systems Group Computing and Communication Services Office University of Illinois at Urbana-Champaign