06-27-2001
Epoch problem
I would like to know if the "Epoch" problem (on September 9, 2001) i.e. when the Unix clock counter will hit 100000000 will create a problem for programs that are dependent on system and server times.
I am presently part of a team that is working on Oracle database on SUN SOLARIS based servers.
There are lots of programs (written in Pro* C) that are dependent on system time. Any such problems on September 9, 2001 will be disastrous for us. I would like to know more about it. Thanks in advance--Vijay
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
i am trying to figure out how i can get a 'Nix box to display
epoch time. Is there a command to do this? Do I know what I am talking about or am I an Idiot? Wait dont answer that last question!!!!! Thanx in advance!!!:confused: (2 Replies)
Discussion started by: Bodhi
2 Replies
2. Shell Programming and Scripting
Guys, i have a question...
I have 2 sets of data say "a" and "a+1" which has values in epoch time..
Question is... if i were to get the time difference where diff = "a+1" - "a"
can i convert it back to real time duration after the subtraction...
OR i need to convert em first before i do the... (1 Reply)
Discussion started by: 12yearold
1 Replies
3. Shell Programming and Scripting
Hi,
i need to convert below date/time format into epoch time
YYYY-m-d H:M
below the example:
a=`date +"%F %H:%M"`
echo $a
Convert $a to epoch time
------------------------------------------------------------------------
lets take an example
if $a=1.03
here i want the epoch time... (3 Replies)
Discussion started by: ali560045
3 Replies
4. News, Links, Events and Announcements
unix epoch time 1234567890 = Fri, 13 Feb 2009 23:31:30 GMT
Any geek parties happening in celebration?
:D (2 Replies)
Discussion started by: BrewDudeBob
2 Replies
5. Shell Programming and Scripting
I need to convert an epoch time from a file into a standard UTC time and output it in the same format but I'm not sure what's the best approach
here's the input file and the bold part is what I need to convert.
1,1,"sys1",60,300000
2,"E:",286511144960
3,1251194521,"E:",0,0... (2 Replies)
Discussion started by: satchy321
2 Replies
6. Shell Programming and Scripting
Hi all!
I have a "simple" problem:
I want to convert a date and time string (YYYYMMDDhhmmss) to epoch (unix time) in a shellscript.
I want to use the "date/time" string as an input to the script, eg:
scriptname.sh 20090918231000 and get the epoch format echoed out.
Is there an... (3 Replies)
Discussion started by: condmaster
3 Replies
7. Shell Programming and Scripting
Hi all,
I got a file with epoch times like this.
1264010700
1264097400
1263529800
1263762900
1263924300
What I want.
I want all epoch times which are > current epoch time written to a file. So everything that is < will be ignored and not written to the file.
Thanks (3 Replies)
Discussion started by: stinkefisch
3 Replies
8. OS X (Apple)
Hi all,
In terminal when I enter:
date -j -f date -j -f "%Y/%m/%d %T" "2011/09/30 13:00:00" +"%s"
The output is:
When I put 2011/09/30 in var A, and I subsequently enter:
date -j -f date -j -f "%Y/%m/%d %T" "${A} 13:00:00" +"%s"
The output is: (10 Replies)
Discussion started by: mosthated
10 Replies
9. Shell Programming and Scripting
Hi,
Can anybody tell me how time is calculated in the below or what is actually being done here?
Also can you explain in simple words about epoch time and why it is used?
Thanks in advance (1 Reply)
Discussion started by: irudayaraj
1 Replies
10. Shell Programming and Scripting
Hi All,
I have a weird problem. I have a session log which is in .bin format. I am converting the .bin file to xml format using Informatica(it is an ETL tool) and unix functionality called "convertLogFiles" . All this is working fine. The session log has a date column. After converting the log... (3 Replies)
Discussion started by: galaxy_rocky
3 Replies
LEARN ABOUT MOJAVE
posix2time
TIME2POSIX(3) BSD Library Functions Manual TIME2POSIX(3)
NAME
time2posix, posix2time -- convert seconds since the Epoch
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <time.h>
time_t
time2posix(time_t t);
time_t
posix2time(time_t t);
DESCRIPTION
IEEE Std 1003.1-1988 (``POSIX.1'') legislates that a time_t value of 536457599 shall correspond to "Wed Dec 31 23:59:59 GMT 1986." This
effectively implies that POSIX time_t's cannot include leap seconds and, therefore, that the system time must be adjusted as each leap
occurs.
If the time package is configured with leap-second support enabled, however, no such adjustment is needed and time_t values continue to
increase over leap events (as a true `seconds since...' value). This means that these values will differ from those required by POSIX by the
net number of leap seconds inserted since the Epoch.
Typically this is not a problem as the type time_t is intended to be (mostly) opaque--time_t values should only be obtained-from and passed-
to functions such as time(3), localtime(3), mktime(3) and difftime(3). However, IEEE Std 1003.1-1988 (``POSIX.1'') gives an arithmetic
expression for directly computing a time_t value from a given date/time, and the same relationship is assumed by some (usually older) appli-
cations. Any programs creating/dissecting time_t's using such a relationship will typically not handle intervals over leap seconds cor-
rectly.
The time2posix() and posix2time() functions are provided to address this time_t mismatch by converting between local time_t values and their
POSIX equivalents. This is done by accounting for the number of time-base changes that would have taken place on a POSIX system as leap sec-
onds were inserted or deleted. These converted values can then be used in lieu of correcting the older applications, or when communicating
with POSIX-compliant systems.
The time2posix() function is single-valued. That is, every local time_t corresponds to a single POSIX time_t. The posix2time() function is
less well-behaved: for a positive leap second hit the result is not unique, and for a negative leap second hit the corresponding POSIX time_t
does not exist so an adjacent value is returned. Both of these are good indicators of the inferiority of the POSIX representation.
The following table summarizes the relationship between time_t and its conversion to, and back from, the POSIX representation over the leap
second inserted at the end of June, 1993.
DATE TIME T X=time2posix(T) posix2time(X)
93/06/30 23:59:59 A+0 B+0 A+0
93/06/30 23:59:60 A+1 B+1 A+1 or A+2
93/07/01 00:00:00 A+2 B+1 A+1 or A+2
93/07/01 00:00:01 A+3 B+2 A+3
A leap second deletion would look like...
DATE TIME T X=time2posix(T) posix2time(X)
??/06/30 23:59:58 A+0 B+0 A+0
??/07/01 00:00:00 A+1 B+2 A+1
??/07/01 00:00:01 A+2 B+3 A+2
[Note: posix2time(B+1) => A+0 or A+1]
If leap-second support is not enabled, local time_t's and POSIX time_t's are equivalent, and both time2posix() and posix2time() degenerate to
the identity function.
SEE ALSO
difftime(3), localtime(3), mktime(3), time(3)
BSD
September 11, 2005 BSD