centos man page for sd_journal_get_cutoff_monotonic_usec

Query: sd_journal_get_cutoff_monotonic_usec

OS: centos

Section: 3

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

SD_JOURNAL_GET_CUTOFF_REALTIME_USEC(3)			sd_journal_get_cutoff_realtime_usec		    SD_JOURNAL_GET_CUTOFF_REALTIME_USEC(3)

NAME
sd_journal_get_cutoff_realtime_usec, sd_journal_get_cutoff_monotonic_usec - Read cut-off timestamps from the current journal entry
SYNOPSIS
#include <systemd/sd-journal.h> int sd_journal_get_cutoff_realtime_usec(sd_journal* j, uint64_t* from, uint64_t* to); int sd_journal_get_cutoff_monotonic_usec(sd_journal* j, sd_id128_t boot_id, uint64_t* from, uint64_t* to);
DESCRIPTION
sd_journal_get_cutoff_realtime_usec() gets the realtime (wallclock) timestamps of the first and last entries accessible in the journal. It takes three arguments: the journal context object and two pointers to 64-bit unsigned integers to store the timestamps in. The timestamps are in microseconds since the epoch, i.e. CLOCK_REALTIME. Either one of the two timestamp arguments may be passed as NULL in case the timestamp is not needed, but not both. sd_journal_get_cutoff_monotonic_usec() gets the monotonic timestamps of the first and last entries accessible in the journal. It takes three arguments: the journal context object, a 128-bit identifier for the boot, and two pointers to 64-bit unsigned integers to store the timestamps. The timestamps are 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 sd_id128_get_boot(3) for more information. The function will return the timestamps for the boot identified by the passed boot ID. Either one of the two timestamp arguments may be passed as NULL in case the timestamp is not needed, but not both.
RETURN VALUE
sd_journal_get_cutoff_realtime_usec() and sd_journal_get_cutoff_monotonic_usec() return 1 on success, 0 if not suitable entries are in the journal or a negative errno-style error code.
NOTES
The sd_journal_get_cutoff_realtime_usec() and sd_journal_get_cutoff_monotonic_usec() interfaces are available as a shared library, which can be compiled and linked to with the libsystemd-journal pkg-config(1) file.
SEE ALSO
systemd(1), sd-journal(3), sd_journal_open(3), sd_journal_get_realtime_usec(3), sd_id128_get_boot(3), clock_gettime(2) systemd 208 SD_JOURNAL_GET_CUTOFF_REALTIME_USEC(3)
Related Man Pages
sd_journal_foreach_backwards(3) - centos
sd_journal_get_cutoff_realtime_usec(3) - centos
sd_journal_seek_cursor(3) - centos
sd_journal_seek_monotonic_usec(3) - centos
sd_journal_seek_tail(3) - centos
Similar Topics in the Unix Linux Community
Difference between two timestamps
comparing time stamps
Compare 2 timestamps
Identifying files with a timestamp greater than a given timestamp
Convert Timestamp in text to Serial Date-Time