>>52171311

C:\Windows\System32>uptime
'uptime' is not recognized as an internal or external command,
operable program or batch file.

router
>13:55:31 up 65 days, 21:11, load average: 0.03, 0.03, 0.04

server
>13:56:08 up 9 days, 15:43, 1 user, load average: 0.07, 0.03, 0.05

security camera, which restarts everyday
>13:56:57 up 10:51, 1 user, load average: 0.30, 0.08, 0.07

test server
>13:57:04 up 21 days, 15:50, 1 user, load average: 0.29, 0.21, 0.14

>>52171326
>windows

File: best server.jpg (28 KB, 544x214) Image search: [Google]

28 KB, 544x214

>>52171311
AYY LMAO

>>52171426
is this real life?

>>52171311
Example:

 13:03:53 up 338 days, 18:22,  5 users,  load average: 0.12, 0.11, 0.13

Some of us don't need to reboot to update our kernels.

>>52171326
>he doesn't have the uptime utility

C:\Windows\System32>uptime
\\CANBERRA has been up for: 0 day(s), 22 hour(s), 16 minute(s), 24 second(s)

15:05:23 up 61 days, 22:45, 1 user, load average 0.62, 0.49, 0.47

>>52171445
Why wouldn't you though? Are you afraid it won't turn back on?

>>52171492
High uptime SLA.

It depends on what you're running - planned restarts are a good thing occasionally so you do test that it does come back OK - but there are some things you want to restart as little as possible, for example back when I used to run an ircd, because netsplits.

>>52171445
>implying you've never hibernated your server
Lol try harder

14:25:29 up 825 days, 19:03, 1 user, load average: 0.02, 0.12, 0.15