Unix time - Revision history

Jsummers: Category:Date and time formats

2017-07-23T15:01:08Z

Category:Date and time formats

Jsummers at 16:15, 28 May 2017

2017-05-28T16:15:29Z

Jsummers: Changed primary category

2015-12-04T19:00:50Z

Changed primary category

Dan Tobias: /* References */

2014-01-22T14:07:09Z

‎References

Dan Tobias at 17:04, 13 January 2013

2013-01-13T17:04:41Z

Dan Tobias at 16:39, 13 January 2013

2013-01-13T16:39:50Z

Dan Tobias: Created page with "{{FormatInfo |formattype=electronic |subcat=Binary Data }} '''Unix time''', or POSIX time, is a representation of a date and time in the form of a number representing the num..."

2013-01-13T16:35:22Z

Created page with "{{FormatInfo |formattype=electronic |subcat=Binary Data }} '''Unix time''', or POSIX time, is a representation of a date and time in the form of a number representing the num..."

New page

{{FormatInfo
|formattype=electronic
|subcat=Binary Data
}}

'''Unix time''', or POSIX time, is a representation of a date and time in the form of a number representing the number of seconds since the "epoch" of January 1, 1970 at 00:00 (midnight) UTC. "Seconds" for this purpose are reckoned so that a calendar day is always exactly 86,400 seconds, which means that leap seconds are skipped in the numbering.

Technically speaking, the modern definition of UTC with leap seconds was not in use until 1972, so the actual definition of the epoch time in 1970 is a bit hazy. However, in practice, the standard simply consists of days of a fixed number of seconds extending indefinitely into the past and future (seconds before 1972 were actually variable in length to match the varying length of the solar day), with the behavior of the count at the exact moment of a leap second slightly irregular.

Many file formats contain timestamps of this form, stored either as a binary-encoded number to some degree of precision, or as [[ASCII]] strings of digits. When stored as binary, the [[endianness]] of the representation is an issue for the file format.

When stored as a signed 32-bit integer, Unix timestamps will overflow at 03:14:08 UTC on 19 January 2038. This may be a software problem similar to the much-hyped "Y2K" problem that occurred when the year 2000 was reached and software using 2-digit years had problems as a result.

Switching to unsigned integers would extend the useful life of the format through 06:28:15 UTC on Sun, 7 February 2106, at the expense of removing the ability to represent times before the epoch with negative numbers.

The more robust solution would be to adopt 64-bit integers, which would support times through the year 292,277,026,596.

If fractional seconds are needed, the number of bits required and the time of overflow will vary. Milliseconds (1/1000 sec) are often used, adding three decimal digits to the representations.

== See also ==
* [[Date and time formats]]

== References ==
* [[Wikipedia:Unix time|Wikipedia article]]
* [http://www.epochconverter.com/ Epoch converter]

← Older revision		Revision as of 15:01, 23 July 2017
Line 41:		Line 41:
	* [http://www.epochconverter.com/ Epoch converter]		* [http://www.epochconverter.com/ Epoch converter]
	* [http://www.iana.org/time-zones Time zone database]		* [http://www.iana.org/time-zones Time zone database]
		+
		+	[[Category:Date and time formats]]

@@ Line 1: / Line 1: @@
 {{FormatInfo
 |formattype=electronic
-|subcat=Binary Data
+|subcat=Elements of File Formats
 }}
@@ Line 29: / Line 29: @@
 [[Category:File format details]]

← Older revision		Revision as of 17:04, 13 January 2013
Line 7:		Line 7:

	Technically speaking, the modern definition of UTC with leap seconds was not in use until 1972, so the actual definition of the epoch time in 1970 is a bit hazy. However, in practice, the standard simply consists of days of a fixed number of seconds extending indefinitely into the past and future (seconds before 1972 were actually variable in length to match the varying length of the solar day), with the behavior of the count at the exact moment of a leap second slightly irregular.		Technically speaking, the modern definition of UTC with leap seconds was not in use until 1972, so the actual definition of the epoch time in 1970 is a bit hazy. However, in practice, the standard simply consists of days of a fixed number of seconds extending indefinitely into the past and future (seconds before 1972 were actually variable in length to match the varying length of the solar day), with the behavior of the count at the exact moment of a leap second slightly irregular.
		+
		+	Times stored in this format are always with respect to UTC, or Greenwich Mean Time for times prior to the institution of the UTC standard (GMT continues to be popularly used as an abbreviation for this sort of time, although it is no longer technically correct). This standard approximates the solar mean time at the Greenwich Meridian (varying by a fraction of a second due to the use of fixed atomic seconds instead of solar seconds), and does not have one-hour jumps for summer or daylight-saving time as civil time zones often do. Any conversion to local civil time is done in the input/output phase when a timestamp is converted.

	Many file formats contain timestamps of this form, stored either as a binary-encoded number to some degree of precision, or as [[ASCII]] strings of digits. When stored as binary, the [[endianness]] of the representation is an issue for the file format.		Many file formats contain timestamps of this form, stored either as a binary-encoded number to some degree of precision, or as [[ASCII]] strings of digits. When stored as binary, the [[endianness]] of the representation is an issue for the file format.

← Older revision		Revision as of 16:39, 13 January 2013
Line 24:		Line 24:
	* [[Wikipedia:Unix time\|Wikipedia article]]		* [[Wikipedia:Unix time\|Wikipedia article]]
	* [http://www.epochconverter.com/ Epoch converter]		* [http://www.epochconverter.com/ Epoch converter]
		+
		+	[[Category:File format details]]

@@ Line 3: / Line 3: @@
 |subcat=Elements of File Formats
 }}
 '''Unix time''', or POSIX time, is a representation of a date and time in the form of a number representing the number of seconds since the "epoch" of January 1, 1970 at 00:00 (midnight) UTC. "Seconds" for this purpose are reckoned so that a calendar day is always exactly 86,400 seconds, which means that leap seconds are skipped in the numbering.
 Technically speaking, the modern definition of UTC with leap seconds was not in use until 1972, so the actual definition of the epoch time in 1970 is a bit hazy. However, in practice, the standard simply consists of days of a fixed number of seconds extending indefinitely into the past and future (seconds before 1972 were actually variable in length to match the varying length of the solar day), with the behavior of the count at the exact moment of a leap second slightly irregular.
@@ Line 19: / Line 19: @@
 If fractional seconds are needed, the number of bits required and the time of overflow will vary. Milliseconds (1/1000 sec) are often used, adding three decimal digits to the representations.
 == See also ==
@@ Line 27: / Line 41: @@
 * [http://www.epochconverter.com/ Epoch converter]
 * [http://www.iana.org/time-zones Time zone database]