Original post below.
Everyone agreed that advfsd before 4.0D (at least) is a cpu hog, and
absent any specific need for it (doubtful, since you can manage it from
the command line) the best thing to do is remove it's link at rc3.d.
Thanks to:
Don Rye <rye_at_jtasc.acom.mil>
Mark Huehls <huehlsm_at_INDY.NAVY.MIL>
alan_at_nabeth.cxo.dec.com
Flannon Jackson <flannon_at_du.edu>
Stephen Mullin <SMullin_at_gecits.GE.com>
K. M. Peterson <KMP_at_wi.mit.edu>
Dr. Tom Blinn <tpb_at_zk3.dec.com>
------------------------------------------------------------------
Bryan Hodgson Astea International
Senior Systems Administrator 455 Business Center Drive
email: bryanh_at_astea.com Horsham, PA 19044
------------------------------------------------------------------
Original ..
I won't claim to understand advfs.
We've got a bunch o' Unix's here (a development shop). One of them is a
400/233 running 4.0b. The runtime queue seems stuck right about 4.0 ..
and there simply isn't a whole lot going on on this box .. two / three
user average. (Our 3.2g box, averaging 20-30 users, has half the
run-time queue.) The biggest hog on the system is advfsd.
Apart from the mandatory stuff, we're just running ufs on the rest of the
file systems.
I haven't a clue. Anyone care to venture some suggestions? Will summarize.
Received on Tue Mar 03 1998 - 13:52:50 NZDT