Thanks to whomever responds to this.
I have posted this in the past, but I haven't persisted because I am
running an
old RHL system (4.2) and because nobody seemed to have any ideas about
what is
going on. BTW, the old system works very nicely for me, for the limited
purposes assigned to the machine running it. Amazing how well RHL ran so
long ago.
Where I live we have lots of power outages. After a power outage that
shuts a Linux system down, one expects to see fsck run on file systems
as a step in the reboot. All of the RHL systems I have used have done
this, including the 4.2 system I am posting about now. I have watched
this process many times.
But, this system hasn't done that for a long, long time. Nor does it run
fsck
at regular intervals based on the count of mounting of the filesystems.
I have noticed no problems with the file systems, etc, but the whole
problem makes me nervous, and I would like to restore the proper
behavior.
I guess I could do a complete reinstall of the system using the RH cd's,
as I originally did when I installed 4.2 over 2.1. That seems an
overkill ...
It would be preferable to know just what package is messed up, if in
fact it is a package problem, and reinstall that package.
But maybe it isn't a package problem. Maybe the kernel is somehow messed
up in regard to this behavior. Then I would need to remake the kernel.
Or maybe the
problem is with a system config file. I'm at a loss ...
Problem is, I just don't know what is going on well enough to fix it
intelligently, or even to investigate it intelligently.
Any thoughts?
Thanks again,
bob jones ([EMAIL PROTECTED])
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
