Sites with longest uptime

1000+ days uptime means somebody hasn't been installing their security updates.
 
From http://uptime.netcraft.com/up/accuracy.html

Why do you not report uptimes for Linux 2.6 or FreeBSD 6 ?


We only report uptimes for systems where the operating system's timer runs at 100Hz or less. Because the TCP code only uses the low 32 bits of the timer, if the timer runs at say 1000Hz, the value wraps around every 49.7 days (whereas at 100Hz it wraps after 497 days). As there are large numbers of systems which have a higher uptime than this, it is not possible to report accurate uptimes for these systems.

The Linux kernel switched to a higher internal timer rate at kernel version 2.5.26. Linux 2.4 used a rate of 100Hz. Linux 2.6 used a timer at 1000Hz (some architectures were using 1000Hz before this), until the default was changed back to 250Hz in May 2006. (An explanation of the HZ setting in Linux.)

FreeBSD versions 4 and 5 used a 100Hz timer, but FreeBSD 6 has moved to a customisable timer with a default setting of 1000Hz.

So unfortunately this means that we cannot give reliable uptime figures for many Linux and FreeBSD servers.
 
aragon said:
I wonder what's wrong with... the uptime command?

(or the system calls it makes)

Nothing wrong with it but Netcraft doesn't have shell access to those servers to issue the command. They use ICMP timestamps.
 
Back
Top