On Fri, Oct 22, 2010 at 11:58 PM, Tim Uckun <[email protected]> wrote: > On Fri, Oct 22, 2010 at 11:40 PM, Rainer Gerhards > <[email protected]> wrote: >> I guess the answer is simply that your file is included at the wrong spot >> into the main config file. Move that code to the top of the main file and it >> will work. Position-dependent rules like this and including via a directory >> does not work well together. >> > > OK I'll try that next. > > I also noticed that postfix is logging to both mail.log and syslog > too. Very strange.. >
putting on the top of the file worked but renaming the config file 00-postfix.conf didn't even though theoretically it should have loaded the 00-postfix conf before the 50-default.conf Other strange happenings.... rsyslog itself is logging to both syslog and messages but postfix is logging to both syslog and mail.log, cron is logging only to syslog. Rsyslog logs twice into messages like this Oct 22 11:02:22 momentumdb rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="9853" x-info="http://www.rsyslog.com";] rsyslogd was HUPed, type 'lightweight'. Oct 22 11:02:22 momentumdb rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="9853" x-info="http://www.rsyslog.com";] rsyslogd was HUPed, type 'lightweight'. and once into syslog Oct 22 11:02:22 momentumdb rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="9853" x-info="http://www.rsyslog.com";] rsyslogd was HUPed, type 'lightweight'. weird.. At least the postgres logging is sorted. Thanks. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
