Xref: utzoo comp.unix.sysv386:7699 comp.sys.att:12231
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!cbnewsl!urban
From: urban@cbnewsl.att.com (john.urban)
Newsgroups: comp.unix.sysv386,comp.sys.att
Subject: Re: sar -d and ESDI drives
Keywords: sar
Message-ID: <1991May3.131449.29943@cbnewsl.att.com>
Date: 3 May 91 13:14:49 GMT
References: <1991May1.153257.18685@bradley.bradley.edu> <1991May02.135710.7757@chinet.chi.il.us>
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 23

In article <1991May02.135710.7757@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes:
>In article <1991May1.153257.18685@bradley.bradley.edu> fred@bradley.bradley.edu (Fred Jaggi) writes:
>]i'm trying to do performance graphs of some 6386 machines running UNIX
>]System V R 3.2.2, but sar -d doesn't show me anything.  this seems to
>]be the case for all the machines with ESDI drives (SCSI and IDE seem
>]to work just fine).  is there any fix available for this?  
>
>	sar -d is broke in most (all?) 386 unix's.  Seems no-one
>	is able to convert the 3b2 based routines in sar for disk
>	monitoring to the pc-bused controllers.  AT&T tried to
>	fix it in their 3.2.3 release, but broke everything else.
					^^^^^^^^^^^^^^^^^^^^^^
					||||||||||||||||||||||

What's everything else?

>
>	-randy
>
>-- 

John Urban
att!garage!jbu