diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2013-06-26 19:47:34 -0400 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2013-06-26 19:47:34 -0400 |
| commit | 74d005783e355acc784d123024e33bbb66ef9ef1 (patch) | |
| tree | 6f03a459398fd5079a645ec830e0154651f4d7dd /man/sd_journal_get_realtime_usec.xml | |
| parent | 909f413d3c572baadf9b13e36e1e90beba42af86 (diff) | |
| download | systemd-74d005783e355acc784d123024e33bbb66ef9ef1.tar.gz | |
man: use <constant> for various constants which look ugly with quotes
Diffstat (limited to 'man/sd_journal_get_realtime_usec.xml')
| -rw-r--r-- | man/sd_journal_get_realtime_usec.xml | 25 |
1 files changed, 13 insertions, 12 deletions
diff --git a/man/sd_journal_get_realtime_usec.xml b/man/sd_journal_get_realtime_usec.xml index 515932c6d8..b57a7c15b2 100644 --- a/man/sd_journal_get_realtime_usec.xml +++ b/man/sd_journal_get_realtime_usec.xml @@ -77,24 +77,25 @@ journal context object and a pointer to a 64 Bit unsigned integer to store the timestamp in. The timestamp is in microseconds since the epoch, - i.e. CLOCK_REALTIME.</para> + i.e. <constant>CLOCK_REALTIME</constant>.</para> <para><function>sd_journal_get_monotonic_usec()</function> - gets the monotonic timestamp of the current - journal entry. It takes three arguments: the journal - context object, a pointer to a 64 Bit unsigned integer - to store the timestamp in as well as a 128 Bit ID - buffer to store the boot ID of the monotonic timestamp + gets the monotonic timestamp of the current journal + entry. It takes three arguments: the journal context + object, a pointer to a 64 Bit unsigned integer to + store the timestamp in as well as a 128 Bit ID buffer + to store the boot ID of the monotonic timestamp in. The timestamp is in microseconds since boot-up of - the specific boot, i.e. CLOCK_MONOTONIC. Since the + the specific boot, + i.e. <constant>CLOCK_MONOTONIC</constant>. Since the monotonic clock begins new with every reboot it only defines a well-defined point in time when used together with an identifier identifying the boot, see <citerefentry><refentrytitle>sd_id128_get_boot</refentrytitle><manvolnum>3</manvolnum></citerefentry> for more information. If the boot ID parameter is - passed NULL the function will fail if the monotonic - timestamp of the current entry is not of the current - system boot.</para> + passed <constant>NULL</constant> the function will + fail if the monotonic timestamp of the current entry + is not of the current system boot.</para> <para>Note that these functions will not work before <citerefentry><refentrytitle>sd_journal_next</refentrytitle><manvolnum>3</manvolnum></citerefentry> @@ -109,7 +110,7 @@ and <function>sd_journal_get_monotonic_usec()</function> returns 0 on success or a negative errno-style error - code. If the boot ID parameter was passed NULL and the + code. If the boot ID parameter was passed <constant>NULL</constant> and the monotonic timestamp of the current journal entry is not of the current system boot, -ESTALE is returned by <function>sd_journal_get_monotonic_usec()</function>.</para> </refsect1> @@ -123,7 +124,7 @@ <function>sd_journal_get_monotonic_usec()</function> interfaces are available as shared library, which can be compiled and linked to with the - <literal>libsystemd-journal</literal> + <constant>libsystemd-journal</constant> <citerefentry><refentrytitle>pkg-config</refentrytitle><manvolnum>1</manvolnum></citerefentry> file.</para> </refsect1> |