5 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hello everyone.
I bought a dell laptop (XPS M1330) online which came without a hard drive. There is a Windows Vista Ultimate OEMAct sticker with product key at the bottom case. I checked dell website (here) for this model and it says this model supports both 32 and 64-bit version of Windows... (4 Replies)
Discussion started by: milhan
4 Replies
2. Shell Programming and Scripting
Hi,
Here is the issue. From the program snippet I have Base: 0x1800000000, Size: 0x3FFE7FFFFFFFF which are of 40 and 56 bits. SO I used use bignum to do the math but summing them up I always failed having correct result.
perl interpreter info,
perl, v5.8.8 built for... (0 Replies)
Discussion started by: rrd1986
0 Replies
3. UNIX for Advanced & Expert Users
Hi.
I need to migrate the whole unix environment from a Unix mp-ras 32 bit to a Linux Suse 64 bit.
1) can i use cpio to copy the data?
2) can i just copy the users from unix to linux or do i have to create them by hand
3) are there any other concerns i should worry about?
thanx (1 Reply)
Discussion started by: mrodrig
1 Replies
4. Red Hat
Hi all,
I'm looking to cover a corner case for an upcoming test cycle. Is there a way to boot a RedHat Advanced Server 4 (update 3) installed on a Power PC machine to use a 32 bit kernel? This would be similar to what is done here -> https://www.unix.com/aix/26204-aix-platform.html
I've done... (0 Replies)
Discussion started by: philrau
0 Replies
5. Programming
Hello,
If i have 2 strings str1 and str2, i would like to copy/concatenate str2 to str1, from 1st bit leaving the 0th bit.
How do i do it? (2 Replies)
Discussion started by: jazz
2 Replies
LEARN ABOUT CENTOS
sd_journal_get_cutoff_monotonic_usec
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)