A count misses many types of possible corruption. If you select the file, then do
LIST FNAME LASTATTRIBUTE that will give you a better, though still incomplete, appraisal of a file's integrity. Karl <quote who="Bob Woodward"> > I'm not sure how through it is but I've always found that just doing a > COUNT > on a file has shown when there's a problem. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Tuesday, September 11, 2007 8:20 AM > To: u2-Users > Subject: [U2] [UV] checking files for corruption > > Hi all, > > UV 10.1.8 > > What is the best way to verify the integrity of a file while users are > accessing (if possible at all)? > > I see that fixtool will set an exclusive file lock when executing without > any options. If I understand correctly, the -start and -stop options will > scan the file setting group locks. Would it work to set -start to 1 and > -stop to the last group in the file? If so, how do I tell what the last > group of the file is? > > Thanks in advance, > > Scott Thompson > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ > -- Karl Pearson Director of I.T. ATS Industrial Supply, Inc. [EMAIL PROTECTED] http://www.atsindustrial.com 800-789-9300 x29 Local: 801-978-4429 Fax: 801-972-3888 "To mess up your Linux PC, you have to really work at it; to mess up a microsoft PC you just have to work on it." ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
