[181408] in North American Network Operators' Group
Re: RES: REMINDER: LEAP SECOND
daemon@ATHENA.MIT.EDU (Jared Mauch)
Tue Jun 23 09:16:36 2015
X-Original-To: nanog@nanog.org
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <59E8C16E83D82B439E20698AAC790B5F01384981B8@ma45>
Date: Tue, 23 Jun 2015 09:16:35 -0400
To: Leonardo Oliveira Ortiz <leonardo.ortiz@marisolsa.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
If you don=92t have NTP enabled your clock may be wrong so it likely =
won=92t impact you.
I=92ve 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:
>=20
> Guys, if we don't have NTP enable on our Linux we still have problem =
with leap second ??
>=20
>=20
>=20
>=20
> -----Mensagem original-----
> De: NANOG [mailto:nanog-bounces@nanog.org] Em nome de Jared Mauch
> Enviada em: ter=E7a-feira, 23 de junho de 2015 10:08
> Para: Harlan Stenn
> Cc: nanog@nanog.org
> Assunto: Re: REMINDER: LEAP SECOND
>=20
>=20
>> On Jun 22, 2015, at 7:06 PM, Harlan Stenn <stenn@ntp.org> wrote:
>>=20
>> Time going backwards is deadly to a number of applications.
>>=20
>> But apparently not to applications you care about.
>=20
> Oh it is a problem, and most handle it very ungracefully, such as =
dovecot which just dies:
>=20
> http://wiki.dovecot.org/TimeMovedBackwards
>=20
> 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).
>=20
> - Jared
