stevens@hsi.UUCP (Richard Stevens) (08/01/86)
In the file <sys/dk.h> the constant DK_NDRIVE is set to 4 so that statistics are collected only for the first 4 drives that are seen by the auto configuration code. We have 5 drives and would really like to collect statistics on all 5 to see where our disk traffic is going. It appears from vax/autoconf.c that changing DK_NDRIVE, and rebuilding the kernel is all that is required. The systats(1) program looks like it'll handle the extra drive also, without any changes. Am I missing something, or is this all that is required ?? Richard Stevens Health Systems International, New Haven, CT ihnp4 ! hsi ! stevens
chris@umcp-cs.UUCP (Chris Torek) (08/04/86)
In article <400@hsi.UUCP> stevens@hsi.UUCP (Richard Stevens) writes: >In the file <sys/dk.h> the constant DK_NDRIVE is set to 4 [...]. >We have 5 drives and would really like to collect statistics on >all 5 [...]. It appears from>vax/autoconf.c that changing DK_NDRIVE, >and rebuilding the kernel is all that is required. The systats(1) >program looks like it'll handle the extra drive also, without any changes. Systat (singular) may need recompilation. I changed DK_NDRIVE to eight, not wanting to bother finding any `char's holding bits in the range [0..DK_NDRIVE), and not having more than six disks on any one machinge. After all our local changes were installed, I did a `cd /usr/src; make clean; make depend; make; make install'. Beware! This takes at least eighteen hours on an otherwise unloaded 750. (Actually, I made all the libraries first, and installed those, then did a full make. It took three days to straighten out all the little errors along the way.) -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1516) UUCP: seismo!umcp-cs!chris CSNet: chris@umcp-cs ARPA: chris@mimsy.umd.edu