Xref: utzoo comp.unix.sysv386:7707 comp.sys.att:12234
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!midway!clout!chinet!randy
From: randy@chinet.chi.il.us (Randy Suess)
Newsgroups: comp.unix.sysv386,comp.sys.att
Subject: Re: sar -d and ESDI drives
Keywords: sar
Message-ID: <1991May03.174350.4395@chinet.chi.il.us>
Date: 3 May 91 17:43:50 GMT
References: <1991May1.153257.18685@bradley.bradley.edu> <1991May02.135710.7757@chinet.chi.il.us> <1991May3.131449.29943@cbnewsl.att.com>
Distribution: na
Organization: Chinet - Chicago Public Access UNIX
Lines: 19

In article <1991May3.131449.29943@cbnewsl.att.com> urban@cbnewsl.att.com (john.urban) writes:
>>	sar -d is broke in most (all?) 386 unix's.  Seems no-one
>>	fix it in their 3.2.3 release, but broke everything else.
>					^^^^^^^^^^^^^^^^^^^^^^
>What's everything else?

	Try "sar 2 9999" or any continuous output parameter.
	Runs for either 8 or 16 iterations then core dumps. 
	AT&T says "oops, use the older version."
	Also, a number of commands produce erroneous output, consisting
	of a "." followed by 5-16 numbers where an integer is expected.
	Also, sag -Ttek has *never* worked.  Outputs numbers in the
	middle of the graph instead of lines and points.  Depends
	on the -s and -e times and how much data there is.

	-randy
-- 
Randy Suess
randy@chinet.chi.il.us