Difference between revisions of "Uptime (command)"
Jump to navigation
Jump to search
| Line 34: | Line 34: | ||
* [[Windows]]: [[systeminfo | find "System Boot Time:"]] | * [[Windows]]: [[systeminfo | find "System Boot Time:"]] | ||
* <code>[[log show]] --style syslog --last 30m | awk '/Enter/ && /[[unlockUIBecomesActive]]/ {print $1 " " $2}'</code> | * <code>[[log show]] --style syslog --last 30m | awk '/Enter/ && /[[unlockUIBecomesActive]]/ {print $1 " " $2}'</code> | ||
| + | * [[Windows]]: <code>[[systeminfo]]</code> | ||
== See also == | == See also == | ||
Revision as of 15:00, 15 September 2022
Linux Ubuntu output:
uptime 09:54:21 up 8 days, 20:20, 1 user, load average: 0.00, 0.00, 0.00
macOS: https://ss64.com/osx/uptime.html
uptime 13:41 up 31 days, 22:06, 3 users, load averages: 1.41 1.26 1.21 system_profiler SPSoftwareDataType | grep boot
Linux:
PacketShaper# uptime System up for 65 days 23 hours 15 mins 22 secs
Related terms
- Docker:
stat /proc/1/cmdline lastreboot,haltdmidecode- PAN-OS:
show system resources | match up - IOS:
show version | inc uptime wmic os get lastbootuptime- podman info | grep uptime
journalctl --list-boots/var/log/wtmp/var/log/btmp- Windows: find "System Boot Time:"
log show --style syslog --last 30m | awk '/Enter/ && /unlockUIBecomesActive/ {print $1 " " $2}'- Windows:
systeminfo
See also
uptime,last,who, pts, tty,journalctl --list-boots, systeminfo , tuptimetop,ntop,htop,atop,iotop,systemd-cgtop,virt-top,stress,slabtop,docker stats,docker top,docker container top,docker-compose top,nmon,tload,kubectl top pod PODNAME,sar,kubectl top,glances,vmstat, gpustat, asitop- Process, zombie process, fork, thread:
ps,tree,pstree,ps axf,proc,pwdx,which,watch,sar -q,tload,uptime, Interrupts,pgrep,tasklist(Windows), Zombie process,pstack,docker ps,docker-compose ps,jobs,acct,process mrelease,pidstat, IPC,pidof
Advertising:
