Re: KLive: Linux Kernel Live Usage Monitor

[Andrea Arcangeli <andrea@suse.de>]

On Tue, Aug 30, 2005 at 11:40:58AM +0200, Rogier Wolff wrote:
> packets also wouldn't. So if it is so unimportant as here, why bother
> with the more overhead of the TCP connection?

I agree TCP isn't needed, I also don't see SSL very useful here, I use
it extensively for other projects and it would have been even simpler to
use SSL over TCP than to use cleartext UDP with twisted, but it was
pointless to hide the contents of the packet on the network, when then I
show all of them on the website ;) So I'd rather save some packet on the
network and some cpu as well.

> A kernel option that is clearly documented what exact info is logged
> would IMHO work better. (A userspace program is technically a better

It's certainly much easier to tweak the kernel config before compiling
the kernel than to edit the mess in /etc/init.d/* with all the
gratuitous differences of the userland flavours.

Clearly it would be an option to keep disabled by default.

The object of the project is to know how much testing a rc/pre kernel
had before release, and most of the testers are supposed to tweak the
config option by themself, so having a config tweak would make it very
easy to setup. It'll be a bit lighter too, twisted currently takes 6m of
RSS on a x86.

However I'm quite neutral, the main advantage of the userland solution
is that it has been orders of magnitude simpler to develop.

I could perhaps write an auto-installer script, that fetches the tac
file with wget and adds a line to /etc/init.d/boot.local to make life
easier.