Re: In recent kernels, sysklogd cannot find map file.

On Sat, 7 Nov 2009, linux fan wrote to Linus and got reply:
>
> "[PATCH] init/version.c: Define version_string only if"
> causes sysklogd to report "Cannot find map"

But isn't that what we _want_.

If we have CONFIG_KALLSYMS, then we do _not_ want sysklogd to try to
interpret kernel addresses, because the kernel will do that itself.

So the sysklogd "Cannot find map" warning is a feature, not a bug.

I think.

               Linus

On Tue, Nov 3, 2009 at 1:35 PM, Martin Schulze <joey_at_infodrom.org> wrote:
> linux fan wrote:
>> On 11/3/09, Alan Jenkins <alan-jenkins_at_tuffmail.co.uk> wrote:
>> >
>> > It's not clear that this is a problem in sysklog.
>> >
>>
>> I found that these messages are coming from the sysklod package:
>>
>> jhalfs_at_lfs:/sources/sysklogd-1.5$ grep "(Inspecting\|Cannot \
>> > find\|Loaded.*symbols\|Symbols match)" *
>> ksym.c: Syslog(LOG_WARNING, "Cannot find map file.");
>> ksym.c: fputs("Cannot find map file.\n", stderr);
>> ksym.c: Syslog(LOG_INFO, "Loaded %d symbols from %s.", num_syms, mapfile);
>>
>> Something about kernels 2.6.27 and later trigger the Cannot find map
>> file message.
>
> Does somebody propose a patch?
>
> Regards,
>
> Joey
>
> --
> MIME - broken solution for a broken design. -- Ralf Baechle
>
>
> --
> To UNSUBSCRIBE, send an email to infodrom-sysklogd-request_at_lists.infodrom.org
> with a subject of "unsubscribe". Trouble? Contact listmaster_at_lists.infodrom.org
>
>
Received on Tue Nov 10 2009 - 04:15:29 CET