Julian Elischer wrote:
not if you use awk to parse the output to cherrypick out the numbers
you are intersted in...
Right. It would be for humans though, not for machines :).
Ed's suggestion sort of makes more sense though...
-Garrett
___
freebsd
Julian Elischer <[EMAIL PROTECTED]> writes:
> Garrett Cooper <[EMAIL PROTECTED]> writes:
> > What about multiline entries with indentation to group fields for
> > "human readable output"?
> not if you use awk to parse the output to cherrypick out the numbers
> you are intersted in...
vmstat alread
Garrett Cooper wrote:
On Feb 1, 2008, at 3:26 AM, Dag-Erling Smørgrav wrote:
vmstat(1) tries very hard to fit everything in 80 columns.
Unfortunately, it's been years since anyone had a machine where none of
the columns overflowed.
[...]
Removing columns is not an acceptable solution (it
On Feb 1, 2008, at 3:26 AM, Dag-Erling Smørgrav wrote:
vmstat(1) tries very hard to fit everything in 80 columns.
Unfortunately, it's been years since anyone had a machine where none
of
the columns overflowed.
[...]
Removing columns is not an acceptable solution (it would break too
man
* Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote:
> vmstat(1) tries very hard to fit everything in 80 columns.
>
> Unfortunately, it's been years since anyone had a machine where none of
> the columns overflowed.
>
> The recent addition of -h helps with the avm and fre columns, but on a
> busy sys
vmstat(1) tries very hard to fit everything in 80 columns.
Unfortunately, it's been years since anyone had a machine where none of
the columns overflowed.
The recent addition of -h helps with the avm and fre columns, but on a
busy system (e.g. a Varnish server on a busy web site), pretty much
eve
6 matches
Mail list logo
