There is no specific message which triggers it. I was just going through the last few days of logs and it appears that any syslog message coming remotely doesn't get processed via the $PROGRAM macro. example; pppd,named,chat,ntpdate,sshd all get logged into the file (NULL). However messages coming from remote host get the $FACILITY macro applied correctly. Do you want to see my logs? My conf? What else would you like to see so i can be more helpful? Chris Scheller System/Network Administration Network One Internet, inc. http://www.networkone.net/ 1.888.GOT-NET1 On Mon, 21 Feb 2000, Balazs Scheidler wrote:
options { sync(0); use_dns(yes); create_dirs(yes); };
log { source("src"); destination("d_facility"); }; log { source("src"); destination("d_program"); };
The $PROGRAM expands as i would expect when recieving messages from the localhost, but when syslog-ng receives remote messages, $PROGRAM gets expanded to a file name (NULL) under the appropriate directory. however remote messages get expanded correctly with the $FACILITY macro. Did i miss something here?
Could you please provide some more context? What is the message which triggers the PROGRAM expansion bug?
-- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu http://lists.balabit.hu/mailman/listinfo/syslog-ng