Date: Mon, 25 Feb 2013 08:50:45 -0600 From: Guy Helmer <guy.helmer@gmail.com> To: mi+thun@aldan.algebra.com, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: =?windows-1252?Q?Re=3A_syslogd_spinning_the_CPU=2C_not_logging?= =?windows-1252?Q?=85?= Message-ID: <FCF6B570-3227-4F49-A58F-5DF27D819929@palisadesystems.com>
index | next in thread | raw e-mail
Regarding a message of yours from a May 2011, I have an 8.3 i386 system where syslogd has been found spinning the CPU a few times in the past week. The stack trace is similar to yours: #0 0x4810cfa9 in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #1 0x4810f890 in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #2 0x48116bbe in free () from /lib/libc.so.7 #3 0x0804c7e6 in init () #4 <signal handler called> #5 0x48194af3 in select () from /lib/libc.so.7 #6 0x0804e147 in main () On this system, syslogd is configured with a pipe to sshguard to monitor failed logins. In my searches, I have not noticed any resolution for this issue -- any chance I've missed one? Thanks, Guyhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FCF6B570-3227-4F49-A58F-5DF27D819929>