Re: Bug#126750: klogd should optionally be started from init(8)
Thanks a lot folks,
you provided good arguments with these two bug reports. I've
considered the issue on my own as well and came to a different
Instead of making syslogd/klogd controlled by init they will now be
restarted by regular cron scripts if they got lost in the meantime.
This requires a running cron, of course. However, after an OOM
situation you are most probably beaten by *something* anyway.
I hope this meets your needs as well.
Computers are not intelligent. They only think they are.
Please always Cc to me when replying to me on the lists.