Date: Tue, 3 Jun 2003 14:01:13 -0500 From: Pete Fritchman <petef@absolutbsd.org> To: Pawel Worach <pawel.worach@telia.com> Cc: current@FreeBSD.org Subject: Re: vmstat -s broken Message-ID: <20030603190113.GA42673@absolutbsd.org> In-Reply-To: <000001c32a00$a3e227e0$4116f00a@corona> References: <000001c32a00$a3e227e0$4116f00a@corona>
next in thread | previous in thread | raw e-mail | index | archive | help
++ 03/06/03 20:47 +0200 - Pawel Worach:
| I don't know for how long this has been broken but vmstat
| always reports 0 (zero) for the number of system calls
| executed which is virtually impossible.
|
| This is on a system built
| FreeBSD darkstar 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Tue Jun 3 02:48:51
| CEST 2003
|
| darkstar# vmstat -s | grep "system calls"
|
| 0 system calls
| darkstar# uptime
FWIW, I also see this behaviour on -current built Feb 13th:
knap.sac(/home/sac1/petef) [258] > vmstat -s | grep system.calls
0 system calls
knap.sac(/home/sac1/petef) [259] > uname -a
FreeBSD knap.sac.fedex.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0:
Thu Feb 13 16:26:14 CST 2003
root@knap.sac.fedex.com:/usr/obj/usr/src/sys/SAC-DELL240-5 i386
knap.sac(/home/sac1/petef) [260] >
--pete
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030603190113.GA42673>