A leap sec causing issues. For about 40 years now, there have been these leap seconds to no real issue. All of these are "go-forwards" and even MS AD (I believe) treat them as a little bump (nothing to see here move along). So unless you have really a tight VPN (non-standard conforming) I'd hope that nothing has happend, and if it did chances are it's etheir coincidence or intentional. I certainly hope I am around to collect on the https://en.wikipedia.org/wiki/Year_2038_problem for retirement. I think we've all seen the "big to do" regarding Y2K to know better Maybe I am wrong, but...
Just my 2¢s -Joe On Tue, Jun 30, 2015 at 10:42 PM, Nicholas Suan <ns...@nonexiste.net> wrote: > Correct, the leap second gets inserted at midnight UTC. > > "Leap seconds can be introduced in UTC at the end of the months of December > > or June, depending on the evolution of UT1-TAI. Bulletin C is mailed every > six months, either to announce a time step in UTC or to confirm that there > will be no time step at the next possible date." > > ftp://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat > > On Tue, Jun 30, 2015 at 11:30 PM, Stefan <netfort...@gmail.com> wrote: >> This was supposed to have happened @midnight UTC, right? Meaning that we >> are past that event. Under which scenarios should people be concerned about >> midnight local time? Lots of confusing messages flying all over... >> On Jun 30, 2015 10:13 PM, <frnk...@iname.com> wrote: >> >>> We experienced our first leap second outage -- our SHE (super head end) is >>> using (old) Motorola encoders and we lost those video channels. They >>> restarted all those encoders to restore service. >>> >>> Frank >>> >>> -- -Joe 920-530-3631
