41–50 of 214 posts
Beginning on September 13, 2020 at 12:26:39 PM Coordinated Universal Time (UTC), un-patched Splunk platform instances will be unable to recognize timestamps from events with dates that are based on Unix time, due to incorrect parsing of timestamp data.
https://docs.splunk.com/Documentation/Splunk/latest/ReleaseN...
How exciting! 1500000000 occured on 07/14/2017 @ 2:40am (UTC), so it seems we'll have to only wait about 3 years until the next one!
All dates describing pattern: code: #!/bin/bash for t in $(seq 0 100000000 $((2* * 31))); do date -u -d @$t +'%s -> %c'; done output: 0 -> Do 01 Jan 1970 00:00:00 UTC 100000000 -> Sa 03 Mär 1973 09:46:40 UTC 200000000 -> Mo 03 Mai 1976 19:33:20 UTC 300000000 -> Do 05 Jul 1979 05:20:00 UTC 400000000 -> Sa 04 Sep 1982 15:06:40 UTC 500000000 -> Di 05 Nov 1985 00:53:20 UTC 600000000 -> Do 05 Jan 1989 10:40:00 UTC 7000000…
So Sunday
Mo Monday
Di Tuesday
Mi Wednesday
Do Thursday
Fr Friday
Sa Saturday
When we one day become a space faring civilization we will probably stop using the gregorian calendar because why would you use that on say Mars? But there really is no reason to get rid of the unix timestamp as a measure of time and this measure may stay around for a long time. This may mean that people in the future might consider 1970 as year zero where modern civilization began.
All dates describing pattern: code: #!/bin/bash for t in $(seq 0 100000000 $((2* * 31))); do date -u -d @$t +'%s -> %c'; done output: 0 -> Do 01 Jan 1970 00:00:00 UTC 100000000 -> Sa 03 Mär 1973 09:46:40 UTC 200000000 -> Mo 03 Mai 1976 19:33:20 UTC 300000000 -> Do 05 Jul 1979 05:20:00 UTC 400000000 -> Sa 04 Sep 1982 15:06:40 UTC 500000000 -> Di 05 Nov 1985 00:53:20 UTC 600000000 -> Do 05 Jan 1989 10:40:00 UTC 7000000…
Day of week abbreviation translations: So Sunday Mo Monday Di Tuesday Mi Wednesday Do Thursday Fr Friday Sa Saturday I think those are German.
When we one day become a space faring civilization we will probably stop using the gregorian calendar because why would you use that on say Mars? But there really is no reason to get rid of the unix timestamp as a measure of time and this measure may stay around for a long time. This may mean that people in the future might consider 1970 as year zero where modern civilization began.
It's extremely weird and IMHO completely ruins the purpose of a timestamp, but it's a compromise for backwards compatibility, since Unix time was created before leap seconds. This hack ensures that the number of seconds in a day remains fixed, an assumption of many systems at the time.
When we one day become a space faring civilization we will probably stop using the gregorian calendar because why would you use that on say Mars? But there really is no reason to get rid of the unix timestamp as a measure of time and this measure may stay around for a long time. This may mean that people in the future might consider 1970 as year zero where modern civilization began.
Next iteration of unix-time should include the concept of local time in context of relativty if we are going to travel or communicate over significant distances.
When we one day become a space faring civilization we will probably stop using the gregorian calendar because why would you use that on say Mars? But there really is no reason to get rid of the unix timestamp as a measure of time and this measure may stay around for a long time. This may mean that people in the future might consider 1970 as year zero where modern civilization began.
There is a very good reason to eventually abandon it: leap seconds. Unix time goes back one second whenever there is a leap second on Earth. It's extremely weird and IMHO completely ruins the purpose of a timestamp, but it's a compromise for backwards compatibility, since Unix time was created before leap seconds. This hack ensures that the number of seconds in a day remains fixed, an assumption of many systems at th…
Number of seconds since a given time seems fine until we're travelling significantly outside of a common reference plane.
* 0x6000 0000