diff options
| author | Chris Down <chris@chrisdown.name> | 2018-10-15 12:55:35 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2018-10-23 14:26:51 +0200 |
| commit | 3f1c1287a96dfc146ce894bd6bfff388cba0ab55 (patch) | |
| tree | 15282aa532acccdb64d3165238311a7144879578 /man/systemd.time.xml | |
| parent | f402ce827daf8556dc5ec058889c031a9dfd55a5 (diff) | |
| download | systemd-3f1c1287a96dfc146ce894bd6bfff388cba0ab55.tar.gz | |
analyze: Add "timespan" command to dump time span in usec
This is useful for a couple of cases, I'm mostly interested in case #1:
1. Verifying "reasonable" values in a trivially scriptable way
2. Debugging unexpected time span parsing directly
Test Plan:
```
% build/systemd-analyze timespan 20
Original: 20
μs: 20
Human: 20us
% build/systemd-analyze timespan 20ms
Original: 20ms
μs: 20000
Human: 20ms
% build/systemd-analyze timespan 20z
Failed to parse time span '20z': Invalid argument
```
Diffstat (limited to 'man/systemd.time.xml')
| -rw-r--r-- | man/systemd.time.xml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/man/systemd.time.xml b/man/systemd.time.xml index 15e1680b8d..24df5ab942 100644 --- a/man/systemd.time.xml +++ b/man/systemd.time.xml @@ -74,6 +74,10 @@ 1y 12month 55s500ms 300ms20s 5day</programlisting> + + <para>One can use the <command>timespan</command> command of + <citerefentry><refentrytitle>systemd-analyze</refentrytitle><manvolnum>1</manvolnum></citerefentry> + to normalise a textual time span for testing and validation purposes.</para> </refsect1> <refsect1> |