uptime has reset itself, but the machine hasnt rebooted

SkiTz0.BiLL-BoB · 03-14-2004, 10:13 AM

Is there somethign I don't know? how can the uptime now be 18hrs when 2 days ago it was 58days (or so).. the machine is a server (SuSE 9) but only has 2 ports open to the world, proftpd and poptop (FTP & VPN) both the latest versions. The rest are behind a router/switch & software firewall.

I've been running this install for 6 months and never has this happened, i've tried a few different ways of getting the uptime, but it seems /proc/uptime is saying 18hrs so all i get back is 18hrs.

I've gone through some logs files, and looked around the time the pc "reset" and nothing unusual, it cant reboot anyway, the boot manager is passworded and all my processes are still fine.

Anybody got any light to shed?

trickykid · 03-14-2004, 10:43 AM

Not totally sure but maybe the /proc/uptime file got reset somehow, maybe deleted, etc.

SkiTz0.BiLL-BoB · 03-14-2004, 12:33 PM

thx for your reply, i've done enough asking around now to answer the question myself... the reason is..

Quote:

this is because you're running a kernel where the "ticks" (the internal
counter the kernel uses to keep time) are ten times more than a regular
kernel. A regular kernel resets the uptime after roughly 497 days, because
the counter can't hold bigger values. Your kernel reaches this level after a
tenth, or about 49.7 days

The higher tick rate is supposed to give a better desktop experience

[ http://lists.suse.com/archive/suse-l...-Jan/3769.html ]

If anybody can tell me how to change this ticks value then please do, otherwise i shall just accept it (even though its a server, not desktop).