Package: slapd Version: 2.4.25-3 Severity: normal slapd spams syslog with "no connection" messages even if no log level is enabled.
| Oct 1 12:06:22 devel slapd[18434]: connection_read(10): no connection! | Oct 1 12:06:22 devel slapd[18434]: connection_read(10): no connection! | Oct 1 12:06:22 devel slapd[18434]: connection_read(10): no connection! A quick check with strace shows that the message is written directly after thread creation: | set_robust_list(0x7f2f668919e0, 0x18) = 0 | sendto(3, "<167>Oct 1 12:06:22 slapd[18434]: connection_read(10): no connection!\n", 71, MSG_NOSIGNAL, NULL, 0) = 71 The source tells me that this may happen in the case of spurious wake-ups. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
