X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsd_journal_get_realtime_usec.xml;h=18fbdca722e0f35ce50d9d1e45a09110f22829cd;hp=515932c6d89fcdf4d8d0ceff4a20d725d1b94a72;hb=9700d6980f7c212b10a69399e6430b82a6f45587;hpb=f274ece0f76b5709408821e317e87aef76123db6;ds=sidebyside diff --git a/man/sd_journal_get_realtime_usec.xml b/man/sd_journal_get_realtime_usec.xml index 515932c6d..18fbdca72 100644 --- a/man/sd_journal_get_realtime_usec.xml +++ b/man/sd_journal_get_realtime_usec.xml @@ -54,15 +54,15 @@ int sd_journal_get_realtime_usec - sd_journal* j - uint64_t* usec + sd_journal *j + uint64_t *usec int sd_journal_get_monotonic_usec - sd_journal* j - uint64_t* usec - sd_id128_t* boot_id + sd_journal *j + uint64_t *usec + sd_id128_t *boot_id @@ -73,28 +73,29 @@ sd_journal_get_realtime_usec() gets the realtime (wallclock) timestamp of the - current journal entry. It takes two arguments: the - journal context object and a pointer to a 64 Bit + current journal entry. It takes two arguments: the + 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. + i.e. CLOCK_REALTIME. sd_journal_get_monotonic_usec() - 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 - monotonic clock begins new with every reboot it only + 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. + The timestamp is in microseconds since boot-up of + the specific boot, + i.e. CLOCK_MONOTONIC. 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 + together with an identifier identifying the boot. See sd_id128_get_boot3 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. + passed NULL, the function will + fail if the monotonic timestamp of the current entry + is not of the current system boot. Note that these functions will not work before sd_journal_next3 @@ -109,7 +110,7 @@ and sd_journal_get_monotonic_usec() 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 NULL and the monotonic timestamp of the current journal entry is not of the current system boot, -ESTALE is returned by sd_journal_get_monotonic_usec(). @@ -121,10 +122,9 @@ sd_journal_get_realtime_usec() and sd_journal_get_monotonic_usec() - interfaces are available as shared library, which can + interfaces are available as a shared library, which can be compiled and linked to with the - libsystemd-journal - pkg-config1 + libsystemd pkg-config1 file.