https://bugzilla.balabit.com/show_bug.cgi?id=89 Summary: DOCUMENTATION: incorrect structure of embedded log statement. Product: syslog-ng Version: 3.1.x Platform: PC OS/Version: Windows Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: alex-pub.balabit@reflexion.net Type of the Report: --- Estimated Hours: 0.0 In syslog-ng-ose-v3.1-guide-admin-en.pdf. Topic "4.5.1. Using embedded log statements" Shows incorrect structure of embedded log statement: log { source(s1); source(s2); ... optional_element(filter1|parser1|rewrite1); optional_element(filter2|parser2|rewrite2);... destination(d1); destination(d2); ... <<<<<<<<<<<<<<<<<<<<<< ! Wrong position ! flags(flag1[, flag2...]); <<<<<<<<<<<<<<<<<<<<<< #embedded log statement log { optional_element(filter1|parser1|rewrite1); optional_element(filter2|parser2|rewrite2);... destination(d1); destination(d2); ... #another embedded log statement log { optional_element(filter1|parser1|rewrite1); optional_element(filter2|parser2|rewrite2);... destination(d1); destination(d2); ... }; }; }; If you follow this structure, the resulting config file will not compile, because `flags` element must appear after the embedded log statement, at least according to cfg-grammar.y: log_stmt : '{' log_items log_forks log_flags '}' { LogPipeItem *pi = log_pipe_item_append_tail($2, $3); $$ = log_connection_new(pi, $4); } ; -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.