




I've also been looking for this info. I've noticed that if I use the gentoo-sources kernel, then Netcraft doesn't detect the OS correctly and records no uptime but when I switch to vanilla-sources, detection and uptimes work correctly. So I'm guessing it must be something patched into the vanilla kernel that's masking this information.jleveille wrote:I have been searching the net for days on this, nothing out there. I do see other Gentoo servers showing in netcrafts surveys. Ah well its not enough to worry about. Thank guys.
Code: Select all
nmap -O <your-webserver>
Code: Select all
Portage 2.0.51.22-r1 (selinux/2005.1/x86, gcc-3.3.5-20050130-hardened,
glibc-2.3.4.20041102-r1, 2.6.11-hardened-r13 i686)
=================================================================
System uname: 2.6.11-hardened-r13 i686 Pentium II (Klamath)
Gentoo Base System version 1.6.12
dev-lang/python: 2.3.5
sys-apps/sandbox: 1.2.8
sys-devel/autoconf: 2.13, 2.59-r6
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5
sys-devel/binutils: 2.15.92.0.2-r7
sys-devel/libtool: 1.5.16
virtual/os-headers: 2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -march=pentium2 -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=pentium2 -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks loadpolicy sandbox selinux sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j4"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="apache2 berkdb crypt curl gd gdbm gif gpm hardened imap ldap libwww maildir
mysql ncurses nls pam pam-mysql pdflib perl png pop postgres python readline
samba sasl selinux snmp ssl tcpd tiff use vhosts x86 xml2 ysql zlib
userland_GNU kernel_linux elibc_glibc"
Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAYCode: Select all
(The 1659 ports scanned but not shown below are in state: filtered)
PORT STATE SERVICE
25/tcp open smtp
80/tcp open http
443/tcp open https
1022/tcp open unknown
Device type: general purpose
Running: Linux 2.6.X
OS details: Linux 2.6.7 - 2.6.8
Uptime 0.444 days (since Mon May 30 14:44:39 2005)
Code: Select all
Operating systems that do not provide uptime information include;
* AIX
* AS/400
* Compaq Tru64
* DG/UX
* Linux before kernel version 2.1
* Linux on Alpha and IA64 processors
* Linux on Intel x86 processor from kernel version 2.5.25 (see below)
* MacOS
* MacOSX
* NT3/Windows 95
* NT4/Windows 98
* NetBSD/OpenBSD
* NetWare
* OS/2
* OS/390
* SCO UNIX
* SunOS 4
* VM
Code: Select all
Why do you not report uptimes for Linux 2.6 or Linux alpha/ia64 ?
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 uses a timer at 1000Hz. (An
explanation of the HZ setting in Linux.)
The above applies to Linux on 32-bit Intel-compatible systems (which is the most
common case). Linux on other platforms uses different timer rates: the Alpha and
Intel ia-64 ports already used 1000Hz, while the ports for sparc, m68k and other
less common processors continue to use 100Hz.
The Linux TCP code only uses the low 32 bits of the timer. Due to the faster
rate of the timer, the value wraps around every 49.7 days (whereas it used to
wrap after 497 days). Because there are large numbers of Linux systems which
have a higher uptime than this, it is no longer possible to report accurate
uptimes for these systems.Code: Select all
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100