Messages in this thread |  | | Date | Wed, 31 Oct 2001 14:39:02 -0700 | From | Andreas Dilger <> | Subject | Re: [Patch] Re: Nasty suprise with uptime |
| |
On Oct 31, 2001 22:05 +0100, Tim Schmielau wrote: > > This means you need to call something that _checks_ the uptime > > (or needs the 64-bit jiffies value) at least once every 1.3 years. > > If you don't do it at least that often, you probably don't care > > about the uptime anyways. > > > > This only impacts anything that really needs a 64-bit jiffies count, > > and has zero impact everywhere else. > > I initially thought of that too. My objection was that boxes with long > uptimes typically get forgotten in a corner until years later someone > checks uptime again. > > However, I fully agree with your importance argument and believe this > proposal to be the best one.
Note that there are several tools that check the uptime, not just the "uptime" command. For example "top" and "w" also display the uptime value (reading /proc/uptime). But yes, if people don't check on their boxes in a year, then this method will lose full multiples of 1.3 years between checks. Probably not a big deal - we can assume such a system is an "appliance" at that point, regardless of what kind of real system it is. If someone wants to ensure their uptime is correct, they can always put "[ -r /proc/uptime ] && cat /proc/uptime > /dev/null" in their cron.monthly directory.
Cheers, Andreas -- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |