On Thu, 13 Jul 2006 18:52:23 CDT, Paul Krizak said:
$ syslog-ng -d -F -f /opt/mpd/vtec/etc/syslog-ng.conf Error in configuration, unresolved destination reference; filter='d_syslog_pipe'
The syntax is fine, it's the semantics that's screwed up here. You had a syntactically correct line that referenced a bad destination.
I believe that the -s switch should mean "if it returns zero, then when you fire up syslog-ng, it *will* start up and begin functioning."
No. The -s switch *can't* guarantee that. Consider all the ways it can fail on the way up - everything from being unable to bind port 514 for listening to not being able to exec() the binary for a destination that pipes to a program. It's even possible that if you run the -s as one user, but actually launch it as root, it will fail because it can't read its config file (consider a /etc/ syslog.conf that's on an NFS mount in a cluster, owned by a user 'syslog' and mode 640 - and the mount squashes root access to 'nobody').