* KLOGD loops continuously calling 'syslog' system call when prink is disabled [not found] ` <94a8a9170806190606r626bc57aq77c46586af97ea05@mail.gmail.com> @ 2008-06-19 13:09 ` Madhu R 2008-06-19 15:34 ` WANG Cong 0 siblings, 1 reply; 2+ messages in thread From: Madhu R @ 2008-06-19 13:09 UTC (permalink / raw) To: LKML Hi All, when I disable printk(CONFIG_PRINTK=n) in the kernel config (2.6.26-rc6), the klogd loops continuously calling the 'syslog' system call. It consumes 99% of the cpu time ( using 'top' command ) . I found similar problem in the kernel mailing list and a patch had gone into the mainline kernel http://linux.derkeiler.com/Mailing-Lists/Kernel/2006-11/msg03317.html In the patch, it returns 'ENOSYS'' while calling 'syslog' system call if printk is disabled. So the klogd keeps on calling this 'syslog' and returns ENOSYS and this process takes most of the CPU time. Please clarify whether I am following correct procedure or this is DEFAULT behavior of klogd. Thanks, madhu. ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: KLOGD loops continuously calling 'syslog' system call when prink is disabled 2008-06-19 13:09 ` KLOGD loops continuously calling 'syslog' system call when prink is disabled Madhu R @ 2008-06-19 15:34 ` WANG Cong 0 siblings, 0 replies; 2+ messages in thread From: WANG Cong @ 2008-06-19 15:34 UTC (permalink / raw) To: Madhu R; +Cc: LKML On Thu, 19 Jun 2008 18:39:10 +0530 "Madhu R" <tuxmadhu@gmail.com> wrote: > Hi All, > > when I disable printk(CONFIG_PRINTK=n) in the kernel config > (2.6.26-rc6), the klogd loops continuously calling the 'syslog' > system call. It consumes 99% of the cpu time ( using 'top' command ) . > I found similar problem in the kernel mailing list and a patch had > gone into the mainline kernel > http://linux.derkeiler.com/Mailing-Lists/Kernel/2006-11/msg03317.html > > In the patch, it returns 'ENOSYS'' while calling 'syslog' > system call if printk is disabled. So the klogd keeps on calling this > 'syslog' and returns ENOSYS and this process takes most of the CPU > time. > > > Please clarify whether I am following correct procedure or > this is DEFAULT behavior of klogd. IIRC, this is the fault of klogd. It doesn't check the return value of syslog(2) (or klogclt(3), a wrapper in glibc) carefully. If you can, please send a patch to sysklogd people. Thanks. -- Hi, I'm a .signature virus, please copy/paste me to help me spread all over the world. ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-06-19 15:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <94a8a9170806190531j7404c96ei4bee3cf5774cbe5a@mail.gmail.com>
[not found] ` <94a8a9170806190559x3d253006ic009b9c4b6714e5b@mail.gmail.com>
[not found] ` <94a8a9170806190606r626bc57aq77c46586af97ea05@mail.gmail.com>
2008-06-19 13:09 ` KLOGD loops continuously calling 'syslog' system call when prink is disabled Madhu R
2008-06-19 15:34 ` WANG Cong
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox