Systeminfo doesn't show uptime on all XP Pro systems
Anyone know how to fix this?
"System Up Time: N/A"
psinfo or other tools can't get uptime neither.
Uptime Project is closing it's doors
After the last very successful 5 years with about 1.7 million data records and more than 20000 active users, we would like to say "thank you" to everyone who helped the project grow to what it is right now.
+++ We are very sad to say it, but we decided to close down the Uptime-Project on the 1st of March 2007. +++
Surely this wasn't an easy decision because of all the time we invested in the project but we don't have enough time to keep the site alive. Another problem is, and always was, the increasing costs for servers and traffic. (Thanks to our sponsors!)
Please shut down all the uptime-clients you're running because we can't keep the domain name forever and we don't want somebody to get his hands on the user data the clients are sending.
Why don't we give away the project for free and let somebody else run it? That question is easy to answer. With more than 20000 users, there is a lot of user data in our database (for example the email-addresses). We don't want somebody to get his hands on this data to maintain the user.s privacy.
Again, thank your very much for competing in the Uptime-Project!
Sincerely the Uptime-Project staff
The content of the email above is not privileged and as such I believe it to be acceptable to post it here. I think the article needs an update as well as alternatives to the Uptime Project.
K.satirli 08:31, 14 February 2007 (UTC)
I just got here. Didnt know about the uptime project. I came a wandering because of this;
[poobear@poobearshouse] # uptime
05:01PM up 13705 days, 15:59, 2 users, load average: 2.24, 4.05, 4.64
Anyone know how that happened? :)
This is not a forum for general discussion about Uptime. Any such comments may be removed or refactored. Please limit discussion to improvement of this article. You may wish to ask factual questions about Uptime at the Reference desk, discuss relevant Wikipedia policy at the Village pump, or ask for help at the Help desk.
Uptime can be abounegligence?
The article states that long uptime can be caused by lack of maintainance, as updates would not be installed. However some systems (such as Linux with KEXEC or IBM Mainframes which run their O/S inside VM) can have the entire system, including O/S kernel reloaded without reboot or interupption of service. —Preceding unsigned comment added by 126.96.36.199 (talk) 19:45, 4 February 2009 (UTC)
Confuses uptime with reliability
As it stands, this article confuses the notion of time since failure with that of availability. Both are sometimes casually referred to as "uptime", but they are different measurements with different units.
The Unix utility uptime prints the time since last reboot -- roughly a measure of time since failure, although rebooting a machine does not always mean service failure. This is also the sense of "uptime" which some hobbyists brag about -- with the implication that having to reboot your machine is a sign that it is unreliable, crashy, or buggy and in need of frequent critical updates.
Availability -- whether measured in "nines" or in defects per million or what-have-you -- is a property of a service, not necessarily an individual machine. This is not at all the same as time since reboot; you can have bad availability without reboots, due to software bugs, overloaded servers, or other problems: a service can be flaky without being hard down.
Other features such as load-balancing, failover, and N-tier architectures make it more complicated to generalize about the availability of a service. But in any event it is important to distinguish time-since-failure from availability. --FOo (talk) 09:00, 19 September 2009 (UTC)
- I agree; this article is mainly about system uptime rather than availability; the high availability article covers the topics you mention above; thus I have removed them from this article. This solves the problem. --Hm2k (talk) 09:36, 26 April 2010 (UTC)
Fifteen or Sixteen seconds?
Or perhaps it is somewhere between the two? In describing the "Five Nines" uptime, the text states five minutes and fifteen seconds; the table shows 16 seconds instead. Which is correct? —Preceding unsigned comment added by 188.8.131.52 (talk) 13:00, 19 April 2010 (UTC)
- This is detailed in the high availability article; so I removed the entry from this article; thus solving the problem anyway. --Hm2k (talk) 09:37, 26 April 2010 (UTC)
add a new wiki page world record uptimes
Are these mainframes that were on 20 years uptime continuously? Do space probes such as pioneer and voyager really have decades long uptime? What is the world record for various systems?
Windows 7 boot time unreliable
It should probably be mentioned that the boot time determined from systeminfo seems to miss out on sleep/hibernate time. If I run my computer for 6 hours but let it sleep for 2, it will show a boot time of 4 hours previous (i.e. current time minus run time where run time excludes sleep time). This has been noted on a number of forums.
I'd update the article, but I have no idea what the rate of time passage is for sleeping/hibernating computers. Presumably, the clock ticks slowly, not at a zero rate. 184.108.40.206 (talk) 00:05, 5 March 2013 (UTC)