[Popcon-developers] maybe a proper fix for #229237

[pere@hungry.com (Petter Reinholdtsen)]

[Bill Allombert]
> We need more test but is seems that:
> 1) /boot/System\.map-(.*). atime match the corresponding kernel boot time
> given by last.

I had a look, and I have three such files, System.map-2.4.27-3-686,
System.map-2.4.27-3-686-smp and System.map-2.6.15-1-686-smp.  The
latter is used.  Their times as reported by stat are

    File: ?/boot/System.map-2.4.27-3-686?
  Access: 2006-08-16 21:46:00.000000000 +0200
  Modify: 2006-05-30 04:09:21.000000000 +0200
  Change: 2006-08-09 21:16:06.000000000 +0200

    File: ?/boot/System.map-2.4.27-3-686-smp?
  Access: 2006-08-16 21:46:00.000000000 +0200
  Modify: 2006-05-30 04:06:05.000000000 +0200
  Change: 2006-08-09 21:16:31.000000000 +0200

    File: ?/boot/System.map-2.6.15-1-686-smp?
  Access: 2006-09-28 08:37:00.000000000 +0200
  Modify: 2006-02-02 19:45:17.000000000 +0100
  Change: 2006-05-01 11:24:42.000000000 +0200

My uptime is 9 days, 16 hours, so the 2006-09-28 access time look
quite correct.  I'm not sure what happened 2006-08-16 nor 2006-08-09.

Do you know what during the boot that is using the System.map file?
Is the kernel reading it, or perhaps klogd or similar?

Friendly,
-- 
Petter Reinholdtsen