When running in a VM:
root@freebsd:/usr/home/jbondc # rsyslogd -v
rsyslogd 7.4.4, compiled with:
FEATURE_REGEXP: Yes
FEATURE_LARGEFILE: Yes
GSSAPI Kerberos 5 support: No
FEATURE_DEBUG (debug build, slow code): No
32bit Atomic operations supported: Yes
64bit Atomic operations supported: Yes
Runtime Instrumentation (slow code): No
uuid support: No
I get 100% CPU usage on every boot, same issue as here:
http://kb.monitorware.com/high-cpu-usage-after-reboot-freebsd-t11973.html
Both on FreeBSD 9.2-RELEASE, and FreeBSD 10-BETA3
It looks like an issue with /dev/console and rsyslogd, this fixes it:
#*.err;kern.warning;auth.notice;mail.crit /dev/console
I broke it down to:
kern.warning;auth.notice;mail.crit /dev/console
*.err
/var/log/err.log
root@freebsd:/usr/home/jbondc # vi /var/log/err.log
2013-12-10T20:40:29.152512-05:00 freebsd rsyslogd: imudp: cannot set thread
scheduling policy, pthread_setschedparam() not available
So it looks like rsyslogd tries to write that message as it loads to
/dev/console and it goes nuts
_______________________________________________
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
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
