[syslog-ng] Some issues with syntax checking

Guillaume Rousse Guillaume.Rousse at inria.fr
Sat Nov 21 15:12:41 CET 2009


Hello list.

Unresolved object errors seems not to be catched by 'syslog-ng 
--syntax-only', whereas they are fatal errors. For instance, with this 
configuration file:
@version:3.0

log { source(s_foo); destination(d_foo); };

[root at oberkampf guillaume]# syslog-ng --syntax-only
[root at oberkampf guillaume]# syslog-ng
Error in configuration, unresolved source reference; source='s_foo'

Moreover, the error message is sometimes a bit misleading. with this 
configuration file:
@version:3.0

source s_foo { unix-stream ("/dev/log" max-connections(100)); };
log { source(s_foo); destination(d_foo); };

[root at oberkampf guillaume]# syslog-ng --syntax-only
[root at oberkampf guillaume]# syslog-ng
Error in configuration, unresolved destination reference; filter='d_foo'

What is missing is a destination, not a filter.
-- 
BOFH excuse #327:

The POP server is out of Coke


More information about the syslog-ng mailing list