Uptime

Uptime is a measure of system reliability, expressed as the period of time a machine, typically a computer, has been continuously working and available. Uptime is the opposite of downtime.

Htop adds an exclamation mark when uptime is longer than 100 days.

It is often used as a measure of computer operating system reliability or stability, in that this time represents the time a computer can be left unattended without crashing or needing to be rebooted for administrative or maintenance purposes.

Conversely, long uptime may indicate negligence, because some critical updates can require reboots on some platforms.<ref>Template:Cite web</ref>

Records

In 2005, Novell reported a server with a 6-year uptime.<ref>Template:Cite web</ref><ref>Template:Cite web</ref> This level of uptime is common when servers are maintained under an industrial context and host critical applications such as banking systems.

Netcraft maintains the uptime records for many thousands of web hosting computers.

A server running Novell NetWare has been reported to have been shut down after 16 years of uptime due to a failing hard disk.<ref>Template:Cite web</ref><ref>Template:Cite web</ref>

Determining system uptime

Unix-like systems (Linux, FreeBSD)

Using uptime

Most Unix-like systems including Linux, FreeBSD, Mac OS X, and SySVr4 have the uptime command. It also displays the system load averages for the past 1, 5, and 15-minute intervals:

<syntaxhighlight lang="console"> user@Linux$ uptime

 18:17:07 up 68 days,  3:57,  6 users,  load average: 0.16, 0.07, 0.06

user@BSD$ uptime 3:01AM up 69 days, 7:53, 0 users, load averages: 0.08, 0.07, 0.05 </syntaxhighlight>

This command originated in 3.0BSD and has become ubiquitous among Unix systems ever since.<ref>Template:Multiref2</ref> Despite almost always providing the same collection of information and being so ubiquitous, it is not part of any Unix-related standard, neither SUS nor POSIX.

On Linux, the uptime command is part of coreutils.

On BSD, the uptime command is hard link to the w program.<ref>Template:Cite web</ref> The w program is based on the RSTS/E, TOPS-10, and TOPS-20 SYSTAT program.<ref>Template:Cite web</ref>

Using system-specific interfaces

Each Unix-like system also has its own private interfaces for obtaining the system uptime.

Linux

On Linux, several procfs files provide information on the system uptime. The main file is Template:Code, but Template:Code provides related information too.<ref>Template:Multiref2</ref>

<syntaxhighlight lang="console"> $ cat /proc/uptime

 350735.47 234388.90

</syntaxhighlight>

The first number is the total number of seconds the system has been up. The second number is how much of that time the machine has spent idle, in seconds.<ref>Template:Cite web</ref> On multi-core systems (and some Linux versions) the second number is the sum of the idle time accumulated by each CPU.<ref>Template:Cite mailing list</ref>

The C API for uptime information is Template:Code.<ref>Template:Man</ref>

BSD

On BSD systems and macOS (a combination of BSD and XNU parts), the uptime information is available from the sysctl system, both in the form of the sysctl command and the Template:Code C function. The sysctl entry is called Template:Code, which provides boot time that can be converted to an uptime by subtracting it from the current time:<ref>Template:Cite web</ref>

<syntaxhighlight lang="console"> $ sysctl kern.boottime kern.boottime: { sec = 1271934886, usec = 667779 } Thu Apr 22 12:14:46 2010 </syntaxhighlight>

macOS also provides the uptime as Template:Code, a POSIX interface with implementation-defined starting point; macOS sets the starting point at system boot.<ref>Template:Cite news</ref> Template:Code and Template:Code are additional ways to access the same raw monotonic clock.

On FreeBSD (but not macOS), the kernel exports three symbols that can be used as Template:Code variables in C to obtain the boot time and uptime. They are called Template:Code, Template:Code, and Template:Code. These require no function call at all to use, unlike Template:Code.<ref>Template:Man</ref> Higher-precision uptime is provided from functions such as Template:Code.<ref>Template:Man</ref>

Microsoft Windows

Windows Task Manager

Windows 7 Task Manager Performance tab screenshot.

Windows 7 Task Manager Performance tab screenshot

Some versions of Microsoft Windows include an uptime field in Windows Task Manager, under the "Performance" tab. The format is D:HH:MM:SS (days, hours, minutes, seconds).

systeminfo

The output of the systeminfo command includes a "System Up Time"<ref>Template:Cite web</ref> or "System Boot Time" field.

<syntaxhighlight lang="doscon"> C:\>systeminfo | findstr "Time:" System Up Time: 0 days, 8 hours, 7 minutes, 19 seconds </syntaxhighlight>

The exact text and format are dependent on the language and locale. The time given by systeminfo is not reliable. It does not take into account time spent in sleep or hibernation. Thus, the boot time will drift forward every time the computer sleeps or hibernates.Template:Citation needed

NET command

The NET command with its STATISTICS sub-command provides the date and time the computer started, for both the NET STATISTICS WORKSTATION and NET STATISTICS SERVER variants. The command NET STATS SRV is shorthand for NET STATISTICS SERVER.<ref>Template:Cite web</ref> The exact text and date format is dependent on the configured language and locale.

<syntaxhighlight lang="doscon"> C:\>NET STATISTICS WORKSTATION | findstr "since" Statistics since 8/31/2009 8:52:29 PM </syntaxhighlight>

Windows Management Instrumentation (WMI)

Uptime can be determined via Windows Management Instrumentation (WMI), by querying the LastBootUpTime property of the Win32_OperatingSystem class.<ref>Template:Cite web</ref> At the command prompt, this can be done using the wmic command:

<syntaxhighlight lang="doscon"> C:\>wmic os get lastbootuptime LastBootUpTime 20110508161751.822066+060 </syntaxhighlight>

The timestamp uses the format yyyymmddhhmmss.nnn, so in the above example, the computer last booted up on 8 May 2011 at 16:17:51.822. The text "LastBootUpTime" and the timestamp format do not vary with language or locale. WMI can also be queried using a variety of application programming interfaces, including VBScript or PowerShell.<ref>Template:Cite web</ref><ref>Template:Cite web</ref>

Uptime.exe

Microsoft formerly provided a downloadable utility called Uptime.exe, which reports elapsed time in days, hours, minutes, and seconds.<ref>Template:Cite web</ref>

<syntaxhighlight lang="doscon"> C:\>Uptime SYSTEMNAME has been up for: 2 day(s), 4 hour(s), 24 minute(s), 47 second(s) </syntaxhighlight>

The time given by Uptime.exe is not reliable. It does not take into account time spent in sleep or hibernation. Thus, the boot time will drift forward every time the computer sleeps or hibernates.Template:Citation needed

FreeDOS

The uptime command is also available for FreeDOS. The version was developed by M. Aitchison.<ref>Template:Cite web</ref>

OpenVMS

On OpenVMS systems, the show system command can be used at the DCL command prompt to obtain the system uptime. The first line of the resulting display includes the system's uptime, displayed as days followed by hours:minutes:seconds. In the following example, the command qualifier /noprocess suppresses the display of per-process detail lines of information.<ref>Template:Cite web</ref>

<syntaxhighlight lang="console"> $ show system/noprocess OpenVMS V7.3-2 on node JACK 29-JAN-2008 16:32:04.67 Uptime 894 22:28:52 </syntaxhighlight>The command output above shows that node JACK on 29 January 2008 at 16:32:04.67 has an uptime of 894 days 22 hours 28 minutes and 52 seconds.

See also

• Availability
• List of POSIX commands
• Maintenance window
• System profiler
• Template:Section link – can allow remote estimation of uptime
• Website monitoring
• Who (Unix) – can display the time the system was booted