Didn't realize this was normal behavior.
"It's not broke, why fix it?"
What happens when the file gets really big?
Does it automatically 'tar' itself and start over?
----- Original Message -----
From: mike <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 14, 2000 7:11 AM
Subject: Re: [newbie] Maximal Mount Count
> Eunice Thompson wrote:
> >
> > Any ideas?
> > ----- Original Message -----
> > From: Eunice Thompson
> > To: [EMAIL PROTECTED]
> > Sent: Thursday, April 13, 2000 7:13 PM
> > Subject: [newbie] Maximal Mount Count
> >
> > ---- Original Message -----
> > From: Eunice Thompson <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, April 13, 2000 9:25 AM
> > Subject: Maximal Mount Count
> >
> > > I booted into mandrake and got an error message that:
> > > "hda3 and hda6 (linux partitions) had reached the maximal mount count,
> > > checked forced ."
> > > I assume this has something to do with /var/log/bootlog
> > > I think I read somewhere that there is a way to automatically remove
old
> > > bootlogs and only keep the last (x) number of entries.
> > > In other words is there a way to automatically reset after 30 days,
and
> > > move the old logs to another file to be put on a floppy?
> > >
> > > Thanks
> > > Eunice
> > >
> > >
>
> AFAIK this is normal behavior, every so many boots the system decides to
> check partitions/disks somewhat like old Micro$oft's Scandisk.
> It can take some time, but is all in all a good idea.
> If it finds errors in the file system it also fixes them.
> Do you wan't to disable this?, or just delete logs, or what?
>
> Rgds:
>
> Mike Perry.
>
