Re: linux-kernel-digest V1 #832

David S. Miller (
Wed, 9 Apr 1997 20:56:50 -0400

Date: Wed, 09 Apr 1997 19:08:48 -0500
From: Evan Jeffrey <>

I had this happen, the trigger was updatedb, as called by cron at
7:40 in my slackware 3.0 distribution. It went untill I killed and
restarted klogd/syslogd. I changed the command like for updatedb
to not include /proc (and some others while I was at it), and the
problem went away. Running "find /proc" does not generate the
error messages, so I don't know exactly what causes it, nor why it
just started with 2.1.32.

Is it opening /proc/kmem perhaps? ;-)