Anybody Is there any reason that nfs lofs and mvfs (clearcase file system) can't be put in FSTYPES= by default.
Does anyone , or better do many monitor nfs mount on your servers this way? lofs and mvfs should be safe bets.
--
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
| _p_ Mike Nemeth
| ___| |_____ email(w) michael.nemeth at lmco.com Work: 856 359-1425
|><___________) | Home Page:http://www.geocities.com/mjnemeth/
| Work Page:http://faraday.motown.lmco.com:3000/~nemethm/
| Work Page:http://ortfsb/~mnemeth/
|++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
On Thu, Jun 08, 2006 at 01:04:09PM -0400, Michael Nemeth wrote:
Anybody Is there any reason that nfs lofs and mvfs (clearcase file system) can't be put in FSTYPES= by default.
Hmm - what's the problem ? FSTYPES gets the filesystem types from the "df -n" command, so it should automatically include all filesystem types currently being used on the box.
The "egrep -v" command afterwards just removes some of them - those that are pseudo filesystems.
Does anyone , or better do many monitor nfs mount on your servers this way? lofs and mvfs should be safe bets.
One reason not to check nfs filesystems is that the df command might hang if there's a network or nfs-server problem.
Regards, Henrik
participants (2)
-
henrik＠hswn.dk
-
michael.nemeth＠lmco.com