> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Glowacki, Tomasz (INFO) > Sent: Thursday, July 01, 2010 11:58 AM > To: rsyslog-users > Subject: Re: [rsyslog] high CPU usage on 5.5.5 and 5.4.0 > > Witam, > > Thursday, July 1, 2010, 11:06:03 AM, you wrote: > > > I ran into this same problem and finally discovered that it was > because > > there were two sets of rsyslog modules, the old ubuntu defaults and > the > > ones I compiled. the wrong ones were being found and problems > resulted. > > > you may find that you have files in /usr/lib/rsyslog and in > > /usr/local/lib/rsyslog > > > delete the wrong ones (probably /usr/lib/rsyslog is the ubuntu > package. > > > rsyslog needs to eventually gain the ability to version the modules > and > > report when the wrong version module is loaded. But at the moment > this is > > not available. > > I don't think it is a good solution. > > If I compile 5.5.0 with --prefix=/my/directory and then make install > is done to that directory rsyslogd should read libs from there (and in > fact - is doing that because omudpspoof module is working). Not from > /usr/lib/rsyslog. Or maybye I'm wrong somewhere... correct me. > > Why rsyslogd is searching for other libs elsewhere than in it's > install directory?
It depends on how you configure the running system (not the build system). There is a command line switch as well as a config directive that tells form where to load modules. Distros usually set their defaults with these directives. To the root question: this may be caused by a bug. I suggest that you check out the current master branch, it may work (which would be an indication of a bug). I did some changes to the code, and I had the impression that what you report could actually something that happens with the older codebase (5.5.5 in this view being "older" ;)). HTH Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
