Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote: > True, true. However, sysklogd and klogd are logging daemons. They deserve > some special treatment IMHO.
Even so, starting it from inittab is too much of a kludge. For one thing, it means that /etc/init.d/syslogd stop will either not work, or be an ugly hack that fools around with inittab. In any case, if the OOM killer has moved onto syslogd, then you've probably lost control of the box anyway so restarting it is pretty pointless. > That is not always possible, and sometimes a kernel VM screwup will cause > it, no? Why should we set up such ugly work arounds for kernel bugs or incompetent admins? -- Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ ) Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
