summaryrefslogtreecommitdiff
path: root/cmd/sbc_harness/static/Documentation/harness_uptime_txt.txt
blob: 09e9243fb52107054dfdf95210c866365e8d8c1c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
NAME
	/harness/uptime.txt

DESCRIPTION
	Reading this file gives a text string of the format

		{ns}ns
		[[[[{y}y]{d}d ]{h}h]{m}m]{s.09}s

	That is: the first line is simply the harness's uptime in an
	integer number of nanoseconds; and the second line is this
	same number in a more human-readable form; divided into
	seconds, minutes, hours, days, and years.

BUGS
	- Using nanoseconds gives the illusion of more precision than
	  there actually is; the harness' clock only has microsecond
	  resolution; the last 3 digits of the returned nanosecond
	  count will always be 0.

	- In the human-readable form, the days are always exactly
	  60*60*24 seconds (leap seconds are ignored), and the years
	  are always exactly 365 days (leap years are ignored).

AUTHOR
	Copyright (C) 2025  Luke T. Shumaker <lukeshu@lukeshu.com>
	SPDX-License-Identifier: AGPL-3.0-or-later