Re: RES: REMINDER: LEAP SECOND

[Jared Mauch <jared () puck nether net>]

If you don’t have NTP enabled your clock may be wrong so it likely won’t impact you.

I’ve always had trouble getting NTP to work right over the years for a variety of reasons.

Just set something in cron to ntpdate -u your host on july 1st and you should be good.

- Jared

> On Jun 23, 2015, at 9:14 AM, Leonardo Oliveira Ortiz <leonardo.ortiz () marisolsa com> wrote:
>
> Guys, if we don't have NTP enable on our Linux we still have problem with leap second ??
>
>
>
>
> -----Mensagem original-----
> De: NANOG [mailto:nanog-bounces () nanog org] Em nome de Jared Mauch
> Enviada em: terça-feira, 23 de junho de 2015 10:08
> Para: Harlan Stenn
> Cc: nanog () nanog org
> Assunto: Re: REMINDER: LEAP SECOND
>
>
> > On Jun 22, 2015, at 7:06 PM, Harlan Stenn <stenn () ntp org> wrote:
> >
> > Time going backwards is deadly to a number of applications.
> >
> > But apparently not to applications you care about.
>
> Oh it is a problem, and most handle it very ungracefully, such as dovecot which just dies:
>
> http://wiki.dovecot.org/TimeMovedBackwards
>
> The issue is also most people are used to using rc.local or rc.* type scripts to spawn a daemon which leads to the 
> next major sysadmin/developer problem with is handling error cases improperly or not at all.  (86401 is perhaps and 
> error case that people should test for).
>
> - Jared