Just for the record, i here have a system cvsupped and built
FreeBSD 5.0-CURRENT #0: Sat Sep 9 13:46:17 CEST 2000
which has a constant load average of 1.00 and higher in uptime, top, and
systat.
The load is already 1.00 or above when the first shell prompt after a boot
appears. I've
On Mon, 11 Sep 2000, Valentin Nechayev wrote:
`top -I' output:
==={
last pid: 811; load averages: 1.01, 0.97, 0.67up 0+00:16:12 23:26:26
This is because the idle process is always running (see "ps lax" outout).
Perhaps the bug is that top doesn't show the idle
Bruce Evans wrote:
On Mon, 11 Sep 2000, Valentin Nechayev wrote:
`top -I' output:
==={
last pid: 811; load averages: 1.01, 0.97, 0.67up 0+00:16:12 23:26:26
This is because the idle process is always running (see "ps lax" outout).
Perhaps the bug is that top
On Mon, 11 Sep 2000, Maxim Sobolev wrote:
Bruce Evans wrote:
Well, the kernel just doesn't treat it specially, so it gets counted in the
load average. I'm not sure if the interrupt and other kernel processes
are counted. Since they do useful work, they should be. The idle process
System in question is:
root@nn:~##uname -mrs
FreeBSD 5.0-CURRENT i386
root@nn:~##grep FreeBSD_version /usr/include/sys/param.h
#undef __FreeBSD_version
#define __FreeBSD_version 500012/* Master, propagated to newvers */
root@nn:~##
cvsup was Sep 8, approximately at 18:00 GMT.
`top -I'
On Sun, 10 Sep 2000, Valentin Nechayev wrote:
`top -I' output:
==={
last pid: 811; load averages: 1.01, 0.97, 0.67up 0+00:16:12 23:26:26
This is because the idle process is always running (see "ps lax" outout).
Perhaps the bug is that top doesn't show the idle process or other
