Re: Bug#126750/749: klogd/sysklogd should optionally be started from init(8)
On Sat, 29 Dec 2001, Marco d'Itri wrote:
> On Dec 29, Henrique de Moraes Holschuh <firstname.lastname@example.org> wrote:
> >> What do people think?
> >Go for it. The OOM killer will hit just about anything which is not a kernel
> >thread, and losing syslogd and klogd is a major no-no.
> The OOM code is supposed to be fixed in 2.4 kernels.
This really is not enough reason to do, or not do the inittab thing. And
there are reports of OOM problems and VM screwups in lkml still.
> I still see no reason to consider klogd more important than e.g. sshd.
Nor do I. I would try do get both into MY inittab...
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot