Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!clout!chinet!randy
From: randy@chinet.chi.il.us (Randy Suess)
Newsgroups: comp.unix.sysv386
Subject: Re: sar -d and ESDI drives
Keywords: sar
Message-ID: <1991May08.192549.8516@chinet.chi.il.us>
Date: 8 May 91 19:25:49 GMT
References: <1991May1.153257.18685@bradley.bradley.edu> <1991May02.135710.7757@chinet.chi.il.us> <3872@sixhub.UUCP>
Organization: Chinet - Chicago Public Access UNIX
Lines: 18

In article <3872@sixhub.UUCP> davidsen@sixhub.UUCP (bill davidsen) writes:
]In article <1991May02.135710.7757@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes:
>
]| 	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.
]
]  Maybe. It was broken in ODT1.0 and seems fixed in the new (1.1?)

	Sorry, I guess I meant "All AT&T based UNIX's"  
	Also, just checked it on my new AT&T sysvr4 v2.1 system
	and all the bugs I know about including -d are fixed.


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