- Original Message -
From: "Bruce Dubbs"
To: "LFS Developers Mailinglist"
Sent: Friday, February 19, 2010 6:39 PM
Subject: Re: klogd and System.map
> linux fan wrote:
> > On 2/19/10, Bruce Dubbs wrote:
> >> My first choice right now is the
linux fan wrote:
> On 2/19/10, Bruce Dubbs wrote:
>> My first choice right now is the script with the unconditional -x as a
>> second choice.
>
> It seems script effectively does unconditional -x because
> it greps for Version_ which is what they removed
> which triggered this whole business.
Wi
Bruce Dubbs wrote:
> Bryan Kadzban wrote:
>> David Jensen wrote:
>>> from slackware rc.syslog
>>> # '-c 3' = display level 'error' or higher messages on console
>> Starting to get off topic now, but after reading the klogd manpage, this
&
On 2/19/10, Bruce Dubbs wrote:
> My first choice right now is the script with the unconditional -x as a
> second choice.
It seems script effectively does unconditional -x because
it greps for Version_ which is what they removed
which triggered this whole business.
Does -x cause loss of informati
Bryan Kadzban wrote:
> David Jensen wrote:
>> Bryan Kadzban wrote:
>>> Bruce Dubbs wrote:
>>>
>>>> To stop klogd from trying to read System.map, it requires passing -x
>>>> in the command line. We can do that easily in the boot scripts.
>&g
David Jensen wrote:
> Bryan Kadzban wrote:
>> Bruce Dubbs wrote:
>>
>>> To stop klogd from trying to read System.map, it requires passing -x
>>> in the command line. We can do that easily in the boot scripts.
>>>
>> Which I would sugge
Bryan Kadzban wrote:
> Bruce Dubbs wrote:
>
>> To stop klogd from trying to read System.map, it requires passing -x
>> in the command line. We can do that easily in the boot scripts.
>>
>
> Which I would suggest if we want to silence the warning. Given
Bruce Dubbs wrote:
> I've noticed an irritating message when klogd starts up. It says:
>
> Cannot find map file.
Meh. I've been skipping the System.map copy (as part of the kernel
install) *forever* -- or at least ever since I moved to kernel 2.6, I
believe -- and never
On 2/18/10, Bruce Dubbs wrote:
> I saw that when I was researching last night. I don't think it is a
> feature. It implies something is wrong. When something is right in
> Linux/Unix, the application should stay silent.
I fussed a lot over this and the warning happen in ksym.c in sysklogd sour
linux fan wrote:
> On 2/18/10, Bruce Dubbs wrote:
>> My understanding is that klogd reads the symbols to translate kernel
>> oops to symbols. I think I saw that the kernel is now doing that
>> internally. In that case, there is no need for klogd to read System.map
>>
On 2/18/10, Bruce Dubbs wrote:
> My understanding is that klogd reads the symbols to translate kernel
> oops to symbols. I think I saw that the kernel is now doing that
> internally. In that case, there is no need for klogd to read System.map
> at all.
That is what Linus said in
Andrew Benton wrote:
> On 18/02/10 20:57, Bruce Dubbs wrote:
>> I've noticed an irritating message when klogd starts up. It says:
>>
>>Cannot find map file.
>>
>> I traced the cause of this message. System.map is a dump of the kernel
>> symbol
On 18/02/10 20:57, Bruce Dubbs wrote:
> I've noticed an irritating message when klogd starts up. It says:
>
>Cannot find map file.
>
> I traced the cause of this message. System.map is a dump of the kernel
> symbols using nm. klogd finds the System.map, but rejects i
I've noticed an irritating message when klogd starts up. It says:
Cannot find map file.
I traced the cause of this message. System.map is a dump of the kernel
symbols using nm. klogd finds the System.map, but rejects it because
there is no symbol with the name "Version_xxx
Greg Schafer wrote:
> Indeed, but IMHO some of the Fedora rationale is questionable ie: "dead
> upstream" is not quite true. That is, if you can believe the sysklogd
> maintainer :-)
>
> http://lists.infodrom.org/infodrom-sysklogd/2007/0011.html
A new release has been made after 6 years. Shock!
Dan Nicholson wrote:
> I just read that Fedora has decided to take the plunge and replace
> sysklogd as their default syslog.
>
> http://fedoraproject.org/wiki/FWN/Issue94#head-f55df1c4e39b27afc053b435a85088e5aec25a84
>
> Anyway, they've decided to use rsyslog since it maintains a compatible
> i
On 5/22/07, Greg Schafer <[EMAIL PROTECTED]> wrote:
> Bruce Dubbs wrote:
>
> > Just to add to this, anduin has been running with syslog-ng from the
> > beginning and it has never had a problem.
>
> Here's a relevant post:
>
> http://linuxfromscratch.org/pipermail/lfs-dev/2005-February/050643.html
>
On Wednesday 23 May 2007 01:36:02 Greg Schafer wrote:
> Here's a relevant post:
>
> http://linuxfromscratch.org/pipermail/lfs-dev/2005-February/050643.html
But how much of that is still valid?
With the latest 2.x of syslog-ng, is it still asynchronous? Based my
experiences and others, I don't th
Bruce Dubbs wrote:
> Just to add to this, anduin has been running with syslog-ng from the
> beginning and it has never had a problem.
Here's a relevant post:
http://linuxfromscratch.org/pipermail/lfs-dev/2005-February/050643.html
But AFAICT the sysklogd maintainership hasn't really improved.. N
Justin R. Knierim wrote:
> Robert Connolly wrote:
>> Syslog-ng was in the LFS book for a short time. It's terrible under load,
>> servers can't use it.
> I haven't had problems with either packages myself, syslog-ng was
> perfectly fine on my dedicateds. Actually at work, we have 2000 shared
> ho
Robert Connolly wrote:
> Syslog-ng was in the LFS book for a short time. It's terrible under load,
> servers can't use it.
I haven't had problems with either packages myself, syslog-ng was
perfectly fine on my dedicateds. Actually at work, we have 2000 shared
hosting servers hosting 500,000 domai
Robert Connolly wrote:
> Syslog-ng was in the LFS book for a short time. It's terrible under load,
> servers can't use it.
Sorry - dsa.physics.usu.ru (an old Pentium-166) logs every SYN and FIN
packet going through its NAT with iptables and syslog-ng, and works just
fine for two full classroom
On Tuesday May 22 2007 02:24:44 pm Douglas J Hunley wrote:
> On Monday 21 May 2007 16:08:02 Robert Connolly wrote:
> > Changes to linux-2.6's printk, and possible other things, have broken
> > klogd's EIP translation. There are no patches available to fix klogd.
>
>
On Monday 21 May 2007 16:08:02 Robert Connolly wrote:
> Changes to linux-2.6's printk, and possible other things, have broken
> klogd's EIP translation. There are no patches available to fix klogd.
Which in my mind just says it's time to switch to syslog-ng and dump plain
Changes to linux-2.6's printk, and possible other things, have broken klogd's
EIP translation. There are no patches available to fix klogd.
See:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=126616
and Suse bug #40651
Adding the '-x' option to klogd's boot script wil
With LFS sysklogd, linux-2.6 with loadable module support, do any of you get
this from /var/log/sys.log:
kernel: No module symbols loaded - kernel modules not enabled.
?
robert
pgpRYZ6HvcLkc.pgp
Description: PGP signature
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://ww
26 matches
Mail list logo
