On Thu, Feb 11, 2010 at 09:23:02PM +0100, Petr Salinger wrote:
The 32-bit overflow during calculation is responsible
for remaining problem.
That overflow is in the kernel itself then? I'm using bc to do these
calculations and it seems ok with large numbers. procps itself uses
long longs. May
The 32-bit overflow during calculation is responsible
for remaining problem.
That overflow is in the kernel itself then?
Yes :-( The kernel uses long, i.e on k-i it is only 32 bit.
The code can use HZ from /usr/include/asm/param.h This is set at 100
This file does not exist on
On Thu, 11 Feb 2010, Craig Small wrote:
On Thu, Feb 11, 2010 at 01:48:07AM +0100, Peter Palfrader wrote:
| wea...@field:~$ cat /proc/uptime ; grep 'cpu ' /proc/stat ; cat
/proc/uptime
| 188847.15 673325.21
| cpu 119994 4473784 3539322 2746621
| 188847.16 673325.21
| wea...@field:~$
On linux, we just use ELF notes and this problem goes away. If there
is something equivalent in freeBSD then I could use that as well.
I wouldn't know, I'm just the poor DSA who gets to fight these machines. :)
Maybe the debian-bsd list would know.
The ELF notes are the property of ELF
On Thu, Feb 11, 2010 at 02:53:45PM +0100, Petr Salinger wrote:
The kernel supplies them. Each note is a pair of name and value.
The GNU/kFreeBSD kernel does not supply note with name AT_CLKTCK.
So that rules out ELF notes.
The old_Hertz_hack appears to be giving widely differing (and wrong)
But looking at poor field.debian.org
188847.15 673325.21
cpu 119994 4473784 3539322 2746621
The second number first line is idle seconds, the 4th number is idle
ticks. See linprocfs_dostat() and linprocfs_douptime().
If its relationship is 100 then one is 100 times the other.
It's not, it's
Petr Salinger petr.salin...@seznam.cz (11/02/2010):
How much cores (CPUs) does field.debian.org have ?
My guess is 4.
Correct:
,
| $ ssh field.debian.org grep ^processor /proc/cpuinfo
| processor : 0
| processor : 1
| processor : 2
| processor : 3
`
Mraw,
KiBi.
On Thu, 11 Feb 2010, Cyril Brulebois wrote:
Petr Salinger petr.salin...@seznam.cz (11/02/2010):
How much cores (CPUs) does field.debian.org have ?
My guess is 4.
Correct:
,
| $ ssh field.debian.org grep ^processor /proc/cpuinfo
| processor : 0
| processor : 1
| processor :
reopen 460331
thanks
I upgraded procps on field.debian.org in the hope of appeasing ps (and
this nagios) but no such luck:
| wea...@field:~$ dpkg -l procps
..
| ii procps 1:3.2.8-6 /proc file system
utilities
| wea...@field:~$ uptime
| Unknown HZ value!
On Wed, Feb 10, 2010 at 02:33:52PM +0100, Peter Palfrader wrote:
I upgraded procps on field.debian.org in the hope of appeasing ps (and
this nagios) but no such luck:
kfreebsd has unbelievably broken procfs so it could be a symptom of
that. Unforuntately the bugs about procfs are several years
On Thu, 11 Feb 2010, Craig Small wrote:
On Wed, Feb 10, 2010 at 02:33:52PM +0100, Peter Palfrader wrote:
I upgraded procps on field.debian.org in the hope of appeasing ps (and
this nagios) but no such luck:
kfreebsd has unbelievably broken procfs so it could be a symptom of
that.
On Thu, Feb 11, 2010 at 01:48:07AM +0100, Peter Palfrader wrote:
| wea...@field:~$ cat /proc/uptime ; grep 'cpu ' /proc/stat ; cat /proc/uptime
| 188847.15 673325.21
| cpu 119994 4473784 3539322 2746621
| 188847.16 673325.21
| wea...@field:~$ getconf CLK_TCK
| 60
I calculate 57 which is
12 matches
Mail list logo
