On Thu, 1 Jul 2010, utf-8?Q?G=C5=82owacki=2C_Tomasz_ ?= wrote: > Hi, > > Thursday, July 1, 2010, 3:26:21 PM, you wrote: > > >> That's what I suspected... > >> So we need to see if it is already fixed or not (master branch). If not, we >> need to look at the debug log and try to find out what is going on. > > Ok, that's my next try. But, I think I'm getting close to the > goal. > > When I comment: > $PrivDropToUser syslog > $PrivDropToGroup adm > > and run the rsyslogd via sudo - it's running perfect with no CPU hog. > It runs as root then. > > Uncommenting that gives CPU hog but running as user syslog. I've > checked file priviledges and they're ok, same as directories, wherever > rsyslogd needs to read/write. > > As I said, 4.2.0 running on the same config, same priviledge level works well.
when I had this problem, logging *.* somewhere showed me 200,000 logs/sec being generated by an error message saying that rsyslog was not allowed to read something. do you have anything similar in your logs? David Lang _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
