Display time system has been running, #users and load

system load averages for the past 1, 5, and 15 minutes.

System load averages not normalized for the number of CPUs. A load average of 1 means a single CPU system is loaded all the time, on a 4 CPU system 1 means it was busy onl;y 25% of the time.

 19:54  up 5 days, 11:58, 7 users, load averages: 1.82 2.12 1.84 
pretty format without loads
up 5 days, 18 hours, 50 minutes
up 3 weeks, 8 hours, 42 minutes
yyyy-mm-dd HH:MM:SS format without loads
2020-01-17 02:42:09
procps version 3.3.12
echo system up for `uptime --pretty | awk  '{ print $2*24+ $4 }'` minutes
system up for 198 minutes
iff < 1 day TODO: check days, weeks...


/var/run/utmp information about who is currently logged on
/proc process information

See : ps(1), top(1), utmp(5)


who is logged in and what they are doing

w [-hin] [user …]

Output a summary of the current activity on the system, including what each user is doing.

The first line displays the current time of day, how long the system has been running, the number of users logged into the system, and the load averages. The load average numbers give the number of jobs in the run queue averaged over 1, 5 and 15 minutes.

The fields output are the user's login name, the name of the terminal the user is on, the host from which the user is logged in, the time the user logged on, the time since the user last typed anything, and the name and arguments of the current process.

21:39:33 up 5 days, 18:57,  1 user,  load average: 0.23, 0.14, 0.10
USER     TTY      FROM             LOGIN@   IDLE   JCPU   PCPU WHAT
pi       pts/0     19:53    0.00s  0.55s  0.05s w
-h Suppress the heading.
-i sorted by idle time.
If one or more user names are specified, the output is restricted to those users. SEE : finger(1), ps(1), , who(1)

Microsoft: Get-Uptime

Uptime [server] [/s ] [/a] [/d:mm/dd/yyyy | /p:n] [/heartbeat] [/? | /help]

server Name or IP address of remote server
/s Display key system events and statistics.
/a Display application failure events (assumes /s).
/d: Only calculate for events after mm/dd/yyyy.
/p: Only calculate for events in the previous n days.
/heartbeat Turn on/off the system's heartbeat
/? Basic usage.
/help Additional usage information.included here next

UPTIME is a utility that processes the machine's event log to determine system availability and current uptime. The target system can either be the local system or a remote system. No special privileges are required for basic operation although it is most accurate to run the tool under an administrative account. Many factors affect these calculations, and the results displayed by this tool should be considered estimates.

Requirements: the system "heartbeat" must be active.

The system "heartbeat" is a date/time stamp that is written to the system registry at a fixed interval. … it can interfere with systems running various forms of power management. It is not recommended to enable the heartbeat of laptop systems.

To enable the heartbeat use: UPTIME /heartbeat [\\Machine]

If the heartbeat is disabled …, UPTIME may report that the event logs do not contain sufficient information to calculate system availability. because UPTIME detects an abnormal shutdown (for instance a bluescreen or power failure) but cannot determine how long the system was down during this abnormal outage.

Run uptime as an administrator for maximum information. When calculating the Current System Uptime, this tool uses the System Performance Counter for Uptime.
If not administrator based on the last recorded boot noted in the event log.

Application Failure event detection is dependent upon Dr Watson being enabled.

Bluescreen detection is dependent upon the system being configured to write an event to the event log if the system stops unexpectedly. To enable bluescreen event logging for Windows NT 4.0: Go to the Control Panel and double click the System Icon. Next select the startup/shutdown tab. Finally check the "Write an event to the system log." check box.

for Windows 2000 Systems : Go to the Control Panel and double click the System Icon. Next select the "Advanced" tab. From the "Advanced" property sheet select the "Startup and Recovery" button. Finally check the "Write an event to the system log." check box.

Potential sources of error: Calculations are based on the entries in the event log. if the event logs have been cleared, or have filled.

The heartbeat is generally written every 5 minutes, so the amount of downtime calculated for abnormal outages is limited in accuracy to this window.

For further information about this tool please see: KB Article: Q232243

\KITCHEN has been up for: 2 day(s), 1 hour(s), 56 minute(s), 3 second(s)

 uptime /s
Uptime Report for: \\KITCHEN

Current OS: Windows 7 Home Premium Multiprocessor Free.
Time Zone: @tzres.dll,-112

System Events as of 1/26/2012 2:22:26 PM:

Date:      Time:        Event:               Comment:
---------- -----------  -------------------  ----------------------------
  1/4/2012 11:21:28 AM  Shutdown
  1/4/2012  5:27:45 PM  Boot                 Prior downtime:0d 6h:6m:17s
  1/5/2012 10:44:14 AM  Shutdown             Prior uptime:0d 17h:16m:29s
  1/5/2012  5:49:11 PM  Boot                 Prior downtime:0d 7h:4m:57s
  1/6/2012  6:39:30 AM  Shutdown             Prior uptime:0d 12h:50m:19s
  1/6/2012  6:40:57 AM  Boot                 Prior downtime:0d 0h:1m:27s
 1/14/2012  1:56:19 PM  Shutdown             Prior uptime:8d 7h:15m:22s
 1/14/2012  1:59:51 PM  Boot                 Prior downtime:0d 0h:3m:32s
On windows 7 uptime crashes here with an Unhandled exception at 0x01008c65 in uptime.exe: 0xC0000005: Access violation reading location 0x00000014.

On Microsoft windows something like uptime

net statistics server

Server Statistics for \\KITCHEN 
Statistics since 1/24/2012 12:13:37 PM

Sessions accepted                  2
Sessions timed-out                 0
Sessions errored-out               139

Kilobytes sent                     1118
Kilobytes received                 4752

Mean response time (msec)          0

System errors                      0
Permission violations              0
Password violations                0

Files accessed                     519
Communication devices accessed     0
Print jobs spooled                 0

Times buffers exhausted

  Big buffers                      0
  Request buffers                  0