Yes, I see that as well. Another symptom is that fsck -p now always announces "unexpected inconsistencies" and drops back to singleuser when it indeed was able to fix the problems, i.e. it marks the filesystem clean and a manual fsck does not report anything unusual.
My last cvsup was with date=2002.06.27.22.00.00 (pre-KSE III, post-UFS2). -- Regards, Georg. Am Mo, 2002-07-08 um 06.41 schrieb Peter Wemm: > It seems to be aborting the 'process all file systems' loop when it modifies > a file system. eg: To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
