Date: Mon, 19 Oct 2009 16:02:17 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: grarpamp <grarpamp@gmail.com> Subject: Re: vmstat -m/-z field parsing Message-ID: <200910191602.17907.jhb@freebsd.org> In-Reply-To: <d2e731a10910151247x22a680a7o9bc747d3c147c9d3@mail.gmail.com> References: <d2e731a10910142324n5b538e4bp9dc782eae8ee46d6@mail.gmail.com> <200910150747.55101.jhb@freebsd.org> <d2e731a10910151247x22a680a7o9bc747d3c147c9d3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 15 October 2009 3:47:59 pm grarpamp wrote: > Sure, it's a workaround for vmstat -z, but not easy for vmstat -m > which has no handy colons/commas to key from. You could key off the number of fields (e.g. using $NF) and assume the first N fields are the name. :) > Shouldn't stats be easy to parse in order to be useful to many > rather than a test of a few users script fu ? :) They should also be easily readable for humans, and I do find the spaces more readable than the underscores FWIW. > Are there detailed docs on what all the fields mean in the various > tools... vmstat -z/-m, systat -vm, netstat -m, top, ps. Most docs > seem to just list the field names a command line switch will display, > instead what sense to make of them. Not really. :-/ -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200910191602.17907.jhb>