Will Andrews <[EMAIL PROTECTED]> wrote:
> Probably the recent change (IIRC) that someone turned running an
> executable into a mtime change.
That was about _atime_ and the discussion was still going on after
I last updated the box. Besides, I verified that simply running
an executable does not
On Thu, Aug 02, 2001 at 06:28:59PM +, Christian Weisgerber ([EMAIL PROTECTED])
wrote:
> An increasing number of executables on that box are sporting ever
> newer mtimes. This appears to have been going on ever since the
> Jul 25 update. There is no clear pattern which executables are
> touc
>On Thu, Aug 02, 2001 at 06:28:59PM +, Christian Weisgerber ([EMAIL PROTECTED])
>wrote:
>> An increasing number of executables on that box are sporting ever
>> newer mtimes. This appears to have been going on ever since the
>> Jul 25 update. There is no clear pattern which executables are
>
The error means that your machine crashed with soft-updates enabled,
leaving 14 blocks and 3 files still allocated on disk (using up
blocks & inodes).
If the error keeps turning up, I would guess that you have a 0 or
empty fsck field in /etc/fstab and fsck -s therefore not fixing the
problem.
