[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
REMINDER: LEAP SECOND
- Subject: REMINDER: LEAP SECOND
- From: guilherme.ganascim at persistelecom.com.br (Guilherme Ganascim)
- Date: Tue, 30 Jun 2015 22:08:28 -0300
- In-reply-to: <CAPkb-7AG8vpHhVB_Vsq2xurO7tBj71X7HjOsDKY-fOuesKHFNA@mail.gmail.com>
- References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <CAPkb-7AG8vpHhVB_Vsq2xurO7tBj71X7HjOsDKY-fOuesKHFNA@mail.gmail.com>
I had problems with Leap Second with mikrotik in versions 6.29.1, 6.28, 6.5 and other versions.
Configured NTP Client in all of them.
Anyone else had this problem?
> On Jun 19, 2015, at 19:30, Baldur Norddahl <baldur.norddahl at gmail.com> wrote:
>
> On 19 June 2015 at 23:58, Harlan Stenn <stenn at ntp.org> wrote:
>
>> Bad idea.
>>
>> When restarting ntpd your clocks will likely be off by a second, which
>> will cause a backward step, which will force the problem you claim to be
>> avoiding.
>>
>
> If you are afraid that your routers will crash due to the leapsecond, then
> it would help to disable the thing that you think will crash them. Even if
> the router crashes when you enable it later on. Because then you can have
> one router crash at a time and have it happen in a service window where you
> are ready for it. Instead of having all routers in your whole network crash
> at exactly the same time.
>
> Regards,
>
> Baldur