Hi,

I'm trying to get the ntpd client working on my OBSD 3.8 server. Problem
is that I keep getting the wrong time. Though I am in the Netherlands,
if I pick .nl ntpd-servers, the time I get is either 1 or 2 hours ahead.
If I select no server at all, I get a time 1 hour ahead.
No such problem on NBSD. Anyone an idea please?

Thanks.

Huub

Huub <v.niekerk@hccnet.nl> wrote:
> Hi,
>
> I'm trying to get the ntpd client working on my OBSD 3.8 server. Problem
> is that I keep getting the wrong time. Though I am in the Netherlands,
> if I pick .nl ntpd-servers, the time I get is either 1 or 2 hours ahead.
> If I select no server at all, I get a time 1 hour ahead.
> No such problem on NBSD. Anyone an idea please?

is your timezone configured correctly?

Begin <43b247a4$0$19147$e4fe514c@dreader28.news.xs4all.n l>
On 2005-12-28, Huub <v.niekerk@hccnet.nl> wrote:
[snip: wrestling with ntpd]
> if I pick .nl ntpd-servers, the time I get is either 1 or 2 hours ahead.
> If I select no server at all, I get a time 1 hour ahead.

Timezones. ntp deals with GMT. Your machine should have its clock set to
GMT, too. Then set the apropriate time zone so date(1) will print the
right time, and automatically adjust for daylight savings time[0] as
well.


[0] ``summer time''.

--
j p d (at) d s b (dot) t u d e l f t (dot) n l .
This message was originally posted on Usenet in plain text.
Any other representation, additions, or changes do not have my
consent and may be a violation of international copyright law.

steven mestdagh wrote:
> Huub <v.niekerk@hccnet.nl> wrote:
>
>>Hi,
>>
>>I'm trying to get the ntpd client working on my OBSD 3.8 server. Problem
>>is that I keep getting the wrong time. Though I am in the Netherlands,
>>if I pick .nl ntpd-servers, the time I get is either 1 or 2 hours ahead.
>>If I select no server at all, I get a time 1 hour ahead.
>>No such problem on NBSD. Anyone an idea please?
>
>
> is your timezone configured correctly?

Yes, during setup I configured the Europe - Amsterdam timezone.

>
> Timezones. ntp deals with GMT. Your machine should have its clock set to
> GMT, too. Then set the apropriate time zone so date(1) will print the
> right time, and automatically adjust for daylight savings time[0] as
> well.
>
>
> [0] ``summer time''.
>

During setup I configured my machine for Europe - Amsterdam. And I
figure that any .nl ntp-server will have that same timezone.

Huub <v.niekerk@hccnet.nl> wrote:
>>
>> Timezones. ntp deals with GMT. Your machine should have its clock set to
>> GMT, too. Then set the apropriate time zone so date(1) will print the
>> right time, and automatically adjust for daylight savings time[0] as
>> well.
>>
>>
>> [0] ``summer time''.
>>
>
> During setup I configured my machine for Europe - Amsterdam. And I
> figure that any .nl ntp-server will have that same timezone.

All NTP servers are using UTC (GMT minus summer time). On account of NTP
being a global protocol, and so on - in fact, pretty much all
time-dependent stuff on the internet is done using UTC.

Oh, and you do know to set your hardware clock to UTC, no?

Joachim

>
> All NTP servers are using UTC (GMT minus summer time). On account of NTP
> being a global protocol, and so on - in fact, pretty much all
> time-dependent stuff on the internet is done using UTC.
>
> Oh, and you do know to set your hardware clock to UTC, no?
>
> Joachim

Well, I still have some odd things here. After some testing using 'date'
I set ntpd.conf to nl.pool.ntp.org. No luck. Then I changed the BIOS
clock to 1 hour before actual time and rebooted: time was ok! Why does
my NetBSD machine work on ntp with all settings actual and my OpenBSD
machine not? I'd think ntp = ntp in the same timezone, no matter what.

Huub <v.niekerk@hccnet.nl> wrote:
>> All NTP servers are using UTC (GMT minus summer time). On account of NTP
>> being a global protocol, and so on - in fact, pretty much all
>> time-dependent stuff on the internet is done using UTC.
>>
>> Oh, and you do know to set your hardware clock to UTC, no?
>
> Well, I still have some odd things here. After some testing using 'date'
> I set ntpd.conf to nl.pool.ntp.org. No luck. Then I changed the BIOS
> clock to 1 hour before actual time and rebooted: time was ok! Why does
> my NetBSD machine work on ntp with all settings actual and my OpenBSD
> machine not? I'd think ntp = ntp in the same timezone, no matter what.

Most UNIXes have, as a default, the hardware clock set to UTC and a
/etc/localtime file detailing the timezone one is in. I remember that,
at least on Linux, there's a configuration option to tell everything
that the clock is set to local time. I imagine other systems would have
similar options, and that it might be enabled by default or by you some
time ago on NetBSD?

Joachim