From: Keith Matthews (postfixfrequentous.co.uk)
Date: Wed Mar 01 2006 - 07:51:00 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, 1 Mar 2006 14:40:29 +0100
Mark Martinec <Mark.Martinec+postfixijs.si> wrote:

> dhawal,
> | I doubt running ntp is a solution.. ntp will sync the time and NOT
> | the date, though i could be mistaken.
>
> You are mistaken.
>
>
> Christophe,
> > It's a good idea... I didn't know ntpdate, thank you, it's more
> > useful for my problem than ntpd that I already use.
>
> ntpdate is being slowly phased out.
> Using ntpd with option -g is now officially the preferred way
> for a reliable start (although some people still tend to favor
> calling ntpdate during startup).
>

Not every platform implements that yet. Nor do all ship ntpdate.

OpenBSD has never (AFAIK) shipped ntpdate, preferring rdate. OBSD's
OpenNTPD has the '-s' flag which says "Set the time immediately at
startup if the local clock is off by more than 180 seconds. Allows for
a large time correction, eliminating the need to run rdate(8) before
starting ntpd"

--
Due to excessive spam as a result of archiving of this list I only
accept mail through the list server.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]