Mailinglist Archive: opensuse (686 mails)

< Previous Next >
Re: [opensuse] Re: convert mount to fstab [SOLVED]
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Sun, 14 Jul 2013 15:03:00 +0200 (CEST)
  • Message-id: <alpine.LNX.2.00.1307141446510.16893@Telcontar.valinor>
Hash: SHA1

On Sunday, 2013-07-14 at 12:26 +0200, lynn wrote:


On the problem client, I used Yast to 'Now and on Boot' for ntp:

2013-07-14T10:44:06.286439+01:00 catral sntp[1247]: Started sntp
2013-07-14T10:44:06.308130+01:00 catral sntp[1247]: kod_init_kod_db(): Cannot
open KoD db file /var/db/ntp-kod
2013-07-14T10:44:06.538097+01:00 catral sntp[1250]: Started sntp
2013-07-14T10:44:06.578755+01:00 catral sntp[1250]: Error looking up (AAAA) Address family for hostname not supported

Isn't four 'A' used for IPv6?

2013-07-14T10:44:22.983921+01:00 catral sntp[1256]: Started sntp
2013-07-14T10:44:23.078058+01:00 catral sntp[1256]: Error looking up (A) Name or service not known

You have a DNS problem there, or you stated the wrong site.

2013-07-14T10:44:23.253676+01:00 catral sntp[1259]: Started sntp
2013-07-14T10:44:23.274654+01:00 catral sntp[1259]: Error looking up (AAAA) Name or service not known
2013-07-14T10:44:32.245859+01:00 catral sntp[1263]: Started sntp
2013-07-14T10:44:32.425933+01:00 catral sntp[1266]: Started sntp
2013-07-14T10:44:32.438542+01:00 catral sntp[1266]: Error looking up (AAAA) Address family for hostname not supported
2013-07-14T10:47:43.038770+01:00 catral sntp[1297]: Started sntp
2013-07-14T10:47:59.224708+01:00 catral systemd[1]: Starting LSB: Network time
protocol daemon (ntpd)...
2013-07-14T10:47:59.655017+01:00 catral ntpd[1349]: ntpd 4.2.6p5@1.2349-o Fri
Mar 1 11:32:25 UTC 2013 (1)
2013-07-14T10:47:59.665276+01:00 catral ntpd[1350]: proto: precision = 2.217
2013-07-14T10:47:59.681385+01:00 catral ntp[1331]: Starting network time
protocol daemon (NTPD)..done
2013-07-14T10:47:59.700763+01:00 catral systemd[1]: Started LSB: Network time
protocol daemon (ntpd).
2013-07-14T10:47:59.725546+01:00 catral ntpd[1350]: ntp_io: estimated max
descriptors: 1024, initial socket boundary: 16
2013-07-14T10:47:59.731827+01:00 catral ntpd[1350]: Listen and drop on 0
v4wildcard UDP 123
2013-07-14T10:47:59.765390+01:00 catral ntpd[1350]: Listen and drop on 1
v6wildcard :: UDP 123
2013-07-14T10:47:59.781972+01:00 catral ntpd[1350]: Listen normally on 2 lo UDP 123
2013-07-14T10:47:59.798260+01:00 catral ntpd[1350]: Listen normally on 3 eth0 UDP 123
2013-07-14T10:47:59.839459+01:00 catral ntpd[1350]: Listen normally on 4 lo ::1
UDP 123
2013-07-14T10:47:59.866824+01:00 catral ntpd[1350]: Listen normally on 5 eth0
fe80::a00:27ff:fe7f:8e13 UDP 123
2013-07-14T10:47:59.873397+01:00 catral ntpd[1350]: peers refreshed
2013-07-14T10:47:59.891603+01:00 catral ntpd[1350]: Listening on routing socket
on fd #22 for interface updates

Why is it an hour slow? If I disable ntp, I get the correct time.

Where do you see above that it is an hour slow?

Is that log for a machine in Spain? The locale is wrong.

The time zone is wrong. The time is wrong. It was installed in UK. It's
now in Spain. Why doesn't the ntp server tell it where it is?

The ntp server does not care where it is placed, because it always use UTC time. It is you who cares where you (not the machine) is, and you have not told the system that the local time is for Spain, not the UK.

I can remember a map of the world screen in Yast installation and
various time options. If I could get back to that, I'd probably be able
to solve this. Is the only way to change the region of a machine by

YaST --> date and time settings. The map is there.

Or simply edit "/etc/sysconfig/clock", the entry:


But then you have to run something that does what SuSEconfig did, but it was deprecated and I don't know what replaces it now.

- -- Cheers,
Carlos E. R.
(from 12.3 x86_64 "Dartmouth" at Telcontar)
Version: GnuPG v2.0.19 (GNU/Linux)

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups