Replying to myself for the sake of the archives. I realized I can use the syslog-ng include functionality to solve my problem; the main config file can just be the @version directive and an include directive to read our real config file renamed to something else. Sorry for the bother... On Mon, 4 Jan 2010, Paul B. Henson wrote:
Our syslog-ng configuration file is generated automatically, from various different bits and pieces based on what roles and services a system provides.
Unfortunately, our current implementation would not allow always ensuring that the "@version" directive is the first line in the generated config file. Version 3 of syslog-ng seems very unhappy if that is not the case. This seems somewhat inflexible, would it be possible to have a command line option specifying the configuration file version so it does not have to be on the very first line of the actual file? Any other suggestions (short of modifying our internal processes :) ) to get verison 3 to be happy with a configuration file without this specific directive as the very first line?
-- Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/ Operating Systems and Network Analyst | henson@csupomona.edu California State Polytechnic University | Pomona CA 91768