From owner-freebsd-current@FreeBSD.ORG Wed Oct 20 06:43:44 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AB96106566C for ; Wed, 20 Oct 2010 06:43:44 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id E3A738FC15 for ; Wed, 20 Oct 2010 06:43:43 +0000 (UTC) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.4/8.14.1) with ESMTP id o9K6hd1h043051; Tue, 19 Oct 2010 23:43:39 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.4/8.13.4/Submit) id o9K6hdkZ043050; Tue, 19 Oct 2010 23:43:39 -0700 (PDT) Date: Tue, 19 Oct 2010 23:43:39 -0700 (PDT) From: Matthew Dillon Message-Id: <201010200643.o9K6hdkZ043050@apollo.backplane.com> To: Alexander Best References: <20101018174331.GA80017@sandvine.com> <20101018181142.GC5644@dan.emsphone.com> <20101018193010.GA88783@sandvine.com> <20101018193916.GD5644@dan.emsphone.com> <20101019001320.GB91234@freebsd.org> Cc: Ed Maste , freebsd-current@freebsd.org, Dan Nelson Subject: Re: CPU report in first line of "vmstat 1" is meaningless X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2010 06:43:44 -0000 :> :> > On a related note I'm not sure if it makes sense to have the same :> > behaviour for the first line when an interval is set as when it is :> > invoked with no interval. : :...also vmstat seems to exist in a few other OSes (linux e.g). maybe they've :fixed it already (or the netbsd/openbsd/dragonflybsd folks or apple?). : :cheers. :alex No, we haven't. I think it is meaningless too, and I can't imagine any script that would try to snarf that line. Another problem is that vmstat output in general is blowing out its column formatting. We have made some changes in DFly... sub-second intervals can be specified, and I think we enforce at least one space between fields so the output doesn't become totally unreadable. But the blowouts still remain. -Matt