Xref: utzoo comp.unix.sysv386:7772 comp.sys.att:12238
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uunet!pmafire!uudell!bigtex!dell!sooner!dewey
From: dewey@dell.dell.com (Dewey Coffman)
Newsgroups: comp.unix.sysv386,comp.sys.att
Subject: Re: sar -d and ESDI drives
Keywords: sar
Message-ID: <1991May4.224214.3599@dell.dell.com>
Date: 4 May 91 22:42:14 GMT
References: <1991May1.153257.18685@bradley.bradley.edu> <1991May02.135710.7757@chinet.chi.il.us>
Organization: Dell Computer Corp.
Lines: 21

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?  

randy>	sar -d is broke in most (all?) 386 unix's.  Seems no-one
randy>	is able to convert the 3b2 based routines in sar for disk
randy>	monitoring to the pc-bused controllers.  AT&T tried to
randy>	fix it in their 3.2.3 release, but broke everything else.

randy>	-randy


	This is fixed in V.4 for 386 unix's.

	dewey
-- 
	Dewey Coffman
	UUCP: dell!sooner!dewey, cs.utexas.edu!dell!sooner!dewey