karmic: changing system logger...

[Daniel J Blueman]

There was discussion about moving from the previously sysklogd to
syslog-ng/rsyslogd in the last development cycle, but we missed the
window.

On jaunty, I find that rsyslogd eats 1.5MB of memory, versus .5MB for
syslog-ng (which I find better for other reasons) [1]. Note that both
are less than the klogd+syslogd's 3.4MB total resident size, so a win
for functionality/capability also.

Particularly on small systems, why blow triple the memory on rsyslogd,
when syslog-ng works just as good (or better)?

Also, when and how can we move on this in karmic?

Thanks,
  Daniel

--- [1]

 VIRT  RES  SHR COMMAND
 6464 2916  252 klogd
12376  488  320 syslogd
19624  804  552 syslog-ng
 118m 1472 1040 rsyslogd
-- 
Daniel J Blueman