Got two replies on this:
Basically - ignore the warnings and leave things the way
they are - although if you do change them it doesn't affect
anything.
Original post:
I'm using unicensus as a way of monitoring my 3.2c system.
(It is very useful BTW)
I think I'm asking the obvious but its nice to have things
confirmed - one of the warnings is that the fsck setting in
fstab is 0 for advfs files systems. It says that root
should be 1 and the others 2.
What impact would changing the setting have? All
filesystems are advfs - /, /usr, /var, & /data
Should I just ignore the warning?
Should i change the settings as suggested?
---------
Alan Rollow - Dr. File System's Home for Wayward Inodes:
--------------------------------------------------------
fsck doesn't get run on AdvFS, it being log based and the
log generally keeping the file system consistent. That's
why the fsck field is set to zero. Sounds like unicensus
doesn't know as much about Digital UNIX as it should.
-------------
Tom Webster:
------------
The setting of zero tells fsck that it is not to run against
the ADVFS volumes. This is correct, fsck is for use with UFS
volumes, not ADVFS.
> Should I just ignore the warning?
Yes
> Should i change the settings as suggested?
No.
---------------------------------------------------------
Craig Silva, Electronic Outreach Program Officer
Victorian Health Promotion Foundation, Melbourne Australia
e-mail: csilva_at_vichealth.vic.gov.au, Tel: 61 3 9345 3211
Post: PO Box 154, Carlton Sth Victoria. 3053. Australia
---------------------------------------------------------
Received on Mon Feb 24 1997 - 01:34:24 NZDT