05-24-2003
The new "X Evolution" skin (recently installed) has timestamps, BTW.
6 More Discussions You Might Find Interesting
1. Solaris
I'm writting a script to find the difference between two timestamp. One field i get on delivery time of the file like 07:17 AM and other is my SLA time 06:30 AM
I need to find the difference between these two time (time exceeded to meet SLA). Need some suggestions. (8 Replies)
Discussion started by: raman1605
8 Replies
2. Shell Programming and Scripting
Hello!
I have the following problem.
I read a file using perl, each line of this file has the fllowing format.
14/4/2008 8:42:03 πμ|10800|306973223399|4917622951117|1||1259|1|126|492|433||19774859454$
Th first field is the timestamp and the second field is the offset in seconds.
How can... (1 Reply)
Discussion started by: chriss_58
1 Replies
3. Shell Programming and Scripting
Hi Friends,
please advise on shell script to add two time stamps
for example :
a=12:32
b=12:00
c=a+b=00:32
please help me to find shell script to add to two time stamps, as i need to convert time from EST to GMT or SST to prepare status of jobs in unix and to specify estimated time to... (3 Replies)
Discussion started by: balireddy_77
3 Replies
4. UNIX for Dummies Questions & Answers
Hi,
i have current timestamp, lets say "12:02:45" in an variable (var1) and another timestamp "08:30:00" fetched from table in another variable2 (var2).
How do i compare 2 timestamps in unix shell scripting.
if var 1 > var 2 then echo message.
Thanks in advance. (3 Replies)
Discussion started by: prasannarajesh
3 Replies
5. Shell Programming and Scripting
Hi all!!,
I'm using Ksh and working on Linux.
I want to compare two timestamps, timestamp1 and timestamp2.
Until, timestamp1 is lesser than timestamp2, i want to do something, lets say print something.
The code i have written is:
a=`date +%H:%M:%S`
b=`date +%H:%M:%S -d" 1... (1 Reply)
Discussion started by: Jayaraman
1 Replies
6. UNIX Benchmarks
CPU/Speed: UltraSPARC-IIIi/1.5Ghz
Ram: 1GB
Motherboard: Sparc
Bus: PCI
Cache:
Controller:
Disk: ATA
Load: 1 user
Kernel: SunOS 5.10 Generic_137111-02
Kernel ELF?: yes
pgms: gcc 2.95.3 compiled
BYTE UNIX Benchmarks (Version 3.11)
System -- SunOS aachen95 5.10... (0 Replies)
Discussion started by: MadeInGermany
0 Replies
LEARN ABOUT CENTOS
sd_journal_get_cutoff_realtime_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)