On Wed, Apr 13, 2011 at 01:20:01AM +0200, Michael Biebl wrote: > Am 13.04.2011 00:21, schrieb Vasilis Vasaitis: > > Package: systemd > > Version: 20-1 > > Severity: important > > > > > > I thought I'd give systemd a try for booting up my laptop, and overall it > > seems to be working well. With one exception though: sometimes when the > > system is running under systemd, I noticed the CPU being pegged at 100%, > > with two processes causing this, klogd and systemd-kmsg-syslogd. When this > > happens, all useful information on dmesg is lost, instead it is full of > > lines like these (in this case, 1348 is the pid of klogd): > > > > I'd be happy to try and debug this, any suggestions on how to proceed? > > Simple answer: stop using sysklogd/klog and use rsyslog. > > sysklogd needs to be updated to support socket activation properly. > > Tollef, should we file bugs against sysklogd and syslog-ng? Reassign/clone > this > bug?
Ah, thanks for that. Perhaps then this should be mentioned in README.Debian? And/or the systemd package (or perhaps the systemd-sysv package) should have appropriate conflicts? As it is, users still running sysklogd/klogd have little chance of finding out the above information. Thanks, Vasilis -- Vasilis Vasaitis "A man is well or woe as he thinks himself so." -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
