W dniu 22.05.2012 13:48, Rainer Gerhards pisze: > Hi Folks, > > just to break the silence: this issue is on my list of things to look at. As > usual, it's just quite busy (and thankfully with paid work as well), so this > waits on a timeslot...
Hi! I know you have many work. I asked Julio about his use case because i have a little problem to reproduce situation on test box. Now meseems i can reproduce problem with maximally stripped config file[1]. This steps should allow to reproduce situation: 1. start rsyslog with given config 2. cat "some text file, a several dozen of lines should be enough" >> /var/log/exim/exim_main.log 3. try to use logger and log any message 4. if it works wait sometime, eventually repeat step 2 5. try to use logger David, you didn't hit such problem because you probably doesn't monitor files and send logs via relp. (In my tests it looks like both situation are needed: filemonitor and sending via relp). Regards, Marcin [1] - config file: $ModLoad immark.so $ModLoad imuxsock.so $ModLoad imklog.so $ModLoad imrelp.so $ModLoad omrelp.so $ModLoad imfile $WorkDirectory /var/spool/rsyslog $ActionQueueType LinkedList $ActionQueueFileName dbq $ActionResumeRetryCount -1 $MainMsgQueueMaxDiskSpace 312M $MainMsgQueueSaveOnShutdown on $MainMsgQueueCheckpointInterval 80 $MainMsgQueueSyncQueueFiles on $MainMsgQueueTimeoutShutdown 10000 $InputFileName /var/log/exim/exim_main.log $InputFileTag meteor.exim_main: $InputFileStateFile meteor.exim_main $InputFileFacility mail $InputFilePollInterval 1 $InputRunFileMonitor *.* :omrelp:10.10.100.101:20514 *.* /var/log/wszystko.log _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards
