Re: linux-kernel-digest V1 #832
Evan Jeffrey (ejeffrey@eliot82.wustl.edu)
Wed, 09 Apr 1997 19:08:48 -0500
>From: "B. James Phillippe" <bryan@Terran.ORG>
>Date: Tue, 8 Apr 1997 23:13:22 -0700 (PDT)
>Subject: [2.1.32] Can't read /proc (!!!)
>
>Greets,
>
> Anyone know what I need to do about this?
>
>Apr 8 08:00:21 earth kernel: Cannot read proc file system.
>Apr 8 08:00:51 earth last message repeated 103105 times
>Apr 8 08:01:52 earth last message repeated 210237 times
>Apr 8 08:02:54 earth last message repeated 213002 times
>Apr 8 08:03:54 earth last message repeated 209197 times
>Apr 8 08:04:55 earth last message repeated 205076 times
>Apr 8 08:05:56 earth last message repeated 208264 times
>Apr 8 08:06:57 earth last message repeated 211380 times
>Apr 8 08:07:58 earth last message repeated 214063 times
>Apr 8 08:08:59 earth last message repeated 208583 times
>Apr 8 08:10:00 earth last message repeated 213169 times
>
>[..........]
>
>That goes on forever. Any ideas? Everything else seems to work okay on
>this box.
>
>thanks,
>- -bp
>- --
># B. James Phillippe # Network/Sys Admin Terran.ORG #
># <bryan@terran.org> # http://w3.terran.org/~bryan #
># Finger for PGP key # Linux Convert - circa 1.1.59 #
># Systems Administrator, Seattle Software Labs, Inc #
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.
Evan Jeffrey
ejeffrey@eliot82.wustl.edu