Re: linux-2.4.0-test11 and sysklogd-1.3-31

2000-12-11 Thread Peter Samuelson
[Georg Nikodym] > + case 'x': > + fprintf(stderr, > + "klogd: %c option is obsolete. Ignoring\n", ch); Clearer (IMHO): "klogd: warning: ignoring obsolete option '-%c'\n", ch); Peter - To unsubscribe from this list: send t

Re: linux-2.4.0-test11 and sysklogd-1.3-31

2000-12-11 Thread Georg Nikodym
> "KO" == Keith Owens <[EMAIL PROTECTED]> writes: KO> Looks good, except that you need to keep the option flags for KO> backwards compatibility. There are a *lot* of scripts out there KO> which invoke klogd with various options and they will fail with KO> this change. It is OK to issue

Re: linux-2.4.0-test11 and sysklogd-1.3-31

2000-12-11 Thread Keith Owens
On Mon, 11 Dec 2000 20:13:46 -0500 (EST), "Georg Nikodym" <[EMAIL PROTECTED]> wrote: >Here's a patch (against sysklogd-1.3-31) that completely tear out the >symbol processing code. Looks good, except that you need to keep the option flags for backwards compatibility. There are a *lot* of script

Re: linux-2.4.0-test11 and sysklogd-1.3-31

2000-12-11 Thread Georg Nikodym
> "GN" == Georg Nikodym <[EMAIL PROTECTED]> writes: GN> Here's a patch (against sysklogd-1.3-31) that completely tear out GN> the symbol processing code. Doh! Forgot a chunk (to be applied after the others): diff -Nru a/src/sysklogd-1.3-31/Makefile b/src/sysklogd-1.3-31/Makefile --- a/sr

Re: linux-2.4.0-test11 and sysklogd-1.3-31

2000-12-11 Thread Georg Nikodym
> "KO" == Keith Owens <[EMAIL PROTECTED]> writes: KO> klogd maps the kernel messages from text to syslog levels and KO> does some fiddling with kernel log levels at start up. It needs KO> to be more than a simple 'cat'. When symbol handling was added KO> to klogd, ksymoops was built int

Re: linux-2.4.0-test11 and sysklogd-1.3-31

2000-12-08 Thread Keith Owens
On Fri, 8 Dec 2000 11:30:06 -0500 (EST), "Georg Nikodym" <[EMAIL PROTECTED]> wrote: >But since you seem to and while we're doing extreme surgery, why have >klogd at all? Every other unix, kernel messages are handled by the >syslog system. What problem did klogd solve and does that problem >stil

Re: linux-2.4.0-test11 and sysklogd-1.3-31

2000-12-08 Thread Georg Nikodym
> "KO" == Keith Owens <[EMAIL PROTECTED]> writes: KO> You only removed the module symbol handling. The problem is that KO> the entire klogd oops handling is out of date and broken. I KO> recommend removing all oops processing from klogd, which means KO> that klogd does not need any symb

Re: linux-2.4.0-test11 and sysklogd-1.3-31

2000-12-07 Thread Keith Owens
On Thu, 7 Dec 2000 12:36:01 -0500 (EST), "Georg Nikodym" <[EMAIL PROTECTED]> wrote: >> "KO" == Keith Owens <[EMAIL PROTECTED]> writes: > > KO> I would prefer to see the oops decoding completely removed from > KO> klogd. > >Since nobody else has weighed in on this issue, I quickly did the >nec

Re: linux-2.4.0-test11 and sysklogd-1.3-31

2000-12-07 Thread Georg Nikodym
> "KO" == Keith Owens <[EMAIL PROTECTED]> writes: KO> I would prefer to see the oops decoding completely removed from KO> klogd. The only justification for klogd converting the oops is KO> to save users from running ksymoops by hand. I would not mind KO> klogd capturing the oops text, f

Re: linux-2.4.0-test11 and sysklogd-1.3-31

2000-12-06 Thread Keith Owens
On Wed, 6 Dec 2000 17:24:58 -0500 (EST), "Georg Nikodym" <[EMAIL PROTECTED]> wrote: >sysklogd 1.3-31 no longer compiles using the latest headers in test11. > >Strictly speaking this isn't a kernel bug... > >sysklogd's ksym_mod.c includes Speaking as the modutils maintainer and the person who ad