john@wa3wbu.UUCP (John Gayman) (01/29/89)
Has anyone successfully gotten sadp to work on uport 3.0e ? I've
tried most of the examples and variations thereof and it always just
kicks back the command usage as if I'm doing something wrong (which is
probably the case). I think the area of confusion is in the device
name. What does it want here ? I've tried:
sadp -h -d disk0 3600
^^^^^
|
|
I've tried everything imaginable here
with no difference.
If someone could clue me in to the secret here I would be grateful.
John
--
John Gayman, WA3WBU | UUCP: uunet!wa3wbu!john
1869 Valley Rd. | ARPA: john@wa3wbu.uu.net
Marysville, PA 17053 | Packet: WA3WBU @ AK3P nusip@maccs.McMaster.CA (Mike Borza) (02/07/89)
In article <218@wa3wbu.UUCP> john@wa3wbu.UUCP (John Gayman) writes: > > Has anyone successfully gotten sadp to work on uport 3.0e ? I've > sadp -h -d disk0 3600 > ^^^^^ > > John > After spending some time trying to get this to work, along with "sar -d", I called my ISC 386/ix vendor. They called back to say that this seems to be broken in the AT&T distribution. Incidentally, it's also broken under uPort SysV/AT rel. 2.3. So much for disk tuning! mike borza <nusip@maccs.uucp or antel!mike@maccs.uucp>