Hi Linux Fan!
It seems there is a possibilty to help with your problem by addding
the -d debug flag to klogd. I.e.
klogd -d
This enables more trace messages to be printed on the console (not in
the log) during the "Inspecting ..." phase. I'm curious to help fix
this issue myself.
Regards
/Joachim
On Tue, Nov 3, 2009 at 6:06 PM, linux fan <linuxscratch_at_gmail.com> 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.
>
>
> --
> 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 03 2009 - 20:49:04 CET
This archive was generated by hypermail 2.2.0 : Tue Nov 03 2009 - 20:49:11 CET