openSuSE 12.3 ntpd

English Network/Internet
1

Installed, and still see System time selected to show UTC
with local time Australia-Sydney

Puzzled to find my time re-set so reads tomorrow…


2013-03-25T18:57:57.167081+11:00 linux-bnn6 ntpd[8007]: Listening on routing socket on fd #22 for interface updates
2013-03-25T18:57:57.174179+11:00 linux-bnn6 ntp[7989]: **Starting network time protocol daemon (NTPD)..done**
2013-03-25T18:57:57.177187+11:00 linux-bnn6 systemd[1]: **Started LSB: Network time protocol daemon (ntpd).**
2013-03-25T18:57:57.244879+11:00 linux-bnn6 gnomesu-pam-backend: pam_unix(gnomesu-pam:session): session closed for user root
2013-03-25T18:58:16.845965+11:00 linux-bnn6 gnomesu-pam-backend: pam_unix(gnomesu-pam:session): session opened for user root by (uid=0)
2013-03-25T18:58:18.030424+11:00 linux-bnn6 kernel: [31016.241507] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
**2013-03-25**T18:58:18.030438+11:00 linux-bnn6 kernel: [31016.241509] EDD information not available.
**2013-03-26**T18:58:35.072885+11:00 linux-bnn6 gnomesu-pam-backend: pam_unix(gnomesu-pam:session): session closed for user root
2013-03-26T18:58:37.369525+11:00 linux-bnn6 gnomesu-pam-backend: pam_unix(gnomesu-pam:session): session opened for user root by (uid=0)
2013-03-26T18:58:38.498104+11:00 linux-bnn6 kernel: [31037.737901] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
2013-03-26T18:58:38.498120+11:00 linux-bnn6 kernel: [31037.737904] EDD information not available.
2013-03-26T19:00:01.853145+11:00 linux-bnn6 run-crons[8341]: logrotate: OK
2013-03-26T19:00:01.861476+11:00 linux-bnn6 run-crons[8341]: mdadm: OK
2013-03-26T19:00:01.869583+11:00 linux-bnn6 run-crons[8341]: packagekit-background.cron: OK
2013-03-26T19:00:01.882217+11:00 linux-bnn6 run-crons[8341]: suse-clean_catman: OK
2013-03-26T19:00:01.968768+11:00 linux-bnn6 run-crons[8341]: suse-do_mandb: OK
2013-03-26T19:00:01.982793+11:00 linux-bnn6 run-crons[8341]: suse.de-backup-rc.config: OK
2013-03-26T19:00:02.251308+11:00 linux-bnn6 run-crons[8341]: suse.de-backup-rpmdb: OK
2013-03-26T19:00:02.260504+11:00 linux-bnn6 run-crons[8341]: **suse.de-check-battery: OK**
2013-03-26T19:00:02.267848+11:00 linux-bnn6 run-crons[8341]: suse.de-cron-local: OK
2013-03-26T19:00:16.096401+11:00 linux-bnn6 gnomesu-pam-backend: pam_unix(gnomesu-pam:session): session closed for user root
2

It is not very clear from your post what you did, what you expected to happen and what happened instead.

Combining the title of your thread with your first word “INstalled” thus asumm me that you installed the ntp package. Which is a bit strange as it is installed by default.

When you then want to let it run (as server/client, both functions are in the saame ntpd daemon), you use YaST > Network Services > NTP configuration (if you have yast2-ntpp-client installed, which is also done by default). And as you show, it is started. So what is the problem?

Running NTP only synchronizes your system time to the outside world. It has nothing to do with any time settings in your system as you seem to assume (but I may interprete that wrongly, brecause you are a biot vague).

Please elaborate a bit on your confusing info:

and still see System time selected to show UTC
with local time Australia-Sydney

and

Puzzled to find my time re-set so reads tomorrow…

3

On 2013-03-25 09:26, paulparker wrote:
>
> Installed, and still see System time selected to show UTC
> with local time Australia-Sydney
>
> Puzzled to find my time re-set so reads tomorrow…

I don’t understand what you mean. Could you please rephrase?

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

4

Here’s my guess.

It is dual booting to some MS o.s. (Windows existed on Unix long before MS, so I won’t let them comandeer the name.). The ntp daemon is not running. The system has been told that the hw clock is at UTC, but it is actually at local time NSW, which is UTC+11. That would give a better than evens chance of the displayed time showing the next day. Or has my brain splurged again?

5

Hi
Set your hardware clock to UTC, do the UTC windows registry tweak so it uses UTC and then set you local timezone in both windows and openSUSE as required.

6

On 2013-03-25 17:06, malcolmlewis wrote:

> Hi
> Set your hardware clock to UTC, do the UTC windows registry tweak so it
> uses UTC and then set you local timezone in both windows and openSUSE as
> required.

What is UTC or GMT Time & a possible issue with openSUSE 12.2 and its
solution.
SDB:Configuring the clock

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

7

For several years only run openSUSE (currently 12.3) on my machines, doing new installation into new separate root and** home** partitions, and noticed the logs datestamped to my local time, rather than UTC time.

In 12.3 logs recording timezone info, fine as UTC makes it easier to know when events occurr.

So would NOT be so surprised IF

timestamp : 2013-03-25T18:58:18.030438+11:00

had changed to
timestamp: 2013-03-25T07:58:18.030438+11:00

or had changed to:
timestamp : 2013-03-26T09:58:18.030438+11:00

however change was the date from 25 to 26 March.

When at “Clock and Time setting” select and currently see in “Clock and Time Zone” :

Region= Australia
Time Zone= NSW (Sydney)
Hardware clock set to UTC = YES
Date and Time (ntp is configured) = 2013-03-26 13:41: 54

(Was my correct current NSW time).

OK my logs were recorded with my local time rather than UTC.

IF my logs all timestamped with correct UTC (Local -11:00 until daylight savings ends) would not be so puzzled.

Wondered IF my hardware clock incorrectly set to local time ?

Considered change “Hardware clock set to UTC = YES” so reads “Hardware clock set to UTC = NO”

However see warning:

You selected local time, but only Linux seems to be installed on your system.
In such case, it is strongly recommended to use UTC, and to click Cancel.

If you want to keep local time, you must adjust the CMOS clock twice the year
because of Day Light Saving switches. If you miss to adjust the clock, backups may fail,
your mail system may drop mail messages, etc.

If you use UTC, Linux will adjust the time automatically.

Do you want to continue with your selection (local time)?

EXIT so no change.

Does the Gnome desktop clock adjust from system time to local time ?

8

Probably displays according to the desktop user’s configuration. (I only use KDE.)

Is this a system time or logfile format question?
What do you get with this?


:~ # echo -e "
 hwclock:" ;hwclock -r ;echo -e "
 date:" ;date ;echo -e "
 ntpd status:" ;systemctl status ntpd.service
9

@paulparker.

I do not quite understand what you say there. There are a lot of “So would NOT be so surprised IF”, which may tell something about you, but nothing of facts on your system.

My idea is still that you have some missconceptions about how time and timestamps are handled in Unix/Linux

Start of this explanation is that the time is set correctly. in a system.

Unix/Linux systems always use UTC internally as the number of seconds that have elapsed since midnight (UTC), 1 January 1970. See Unix time - Wikipedia, the free encyclopedia

You will almost never see this number (but you can by e.g. dumping file entries in a directory where the creation timestamp, etc. of a file are stored, or dump the contents of the system log files). The time shown to any user is converted using his/her timezonee settings (in the environment of his/her processes). Example:

henk@boven:~/test> touch file
henk@boven:~/test> ls -l file
-rw-r--r-- 1 henk wij 0 26 mrt 10:31 file
henk@boven:~/test> TZ=UTC ls -l file
-rw-r--r-- 1 henk wij 0 26 mrt 09:31 file
henk@boven:~/test> TZ='Australia/Brisbane' ls -l file
-rw-r--r-- 1 henk wij 0 26 mrt 19:31 file
henk@boven:~/test>

As you see, when I have a user account on your system (being in Australia) and I of course have my TZ set to Netherlands/Amsterdam’ because I am loged in from the Netherlands, I see a different timestamp on that file than you will see when you have set your time zone properly at ‘Australia/Brisbane’. But internally it is all in seconds since the Epoch.

This is also how things like Summer Time (Daylight Saving Time) are handled. There is a database of all rules (defined by all the different governements in the world) that contains information about the begin/end of it. And it will influence how a timestamp is shown to you.

Now how does your system get the correct time in the first place?
At boot the system time is taken from the (CMOS) battery powered clock inside your system. When you use NTP as a client (which I advise you to do), as soon as the network comes up and the confifured NTP server can be reached, that time is corrected (because the hardwate clock is not that precise) and NTP keeps correcting during the up time of the system. This is how your Linux system is using it’s correct UTC time all the time. And at shutdown, the hardware clock is set to the time as it is then, again beacuse the hardwarte clock might have got out of sync during the up time of the system.

This is all not to difficult to uderstand. But now Windows gets into the game :(. Windows also uses the hardware clock at boot and sets it at shutdwon. But Windows (this is now gettig different the last few years btw) had no concept on how to handle world wide time. Thus it sets the hardware clock to the time the Windows end-users uses: local time. Now imagine what happens when you have a multi boot situation! This is why there is a special setting to set at shutdown and read at boot the hardware clock in local time. But it does not change the Linux system itself allways running in UTC. It of course corrects the local time read at boot from the hardware clock into UTC before it realy starts to use the system clock.

And imagine how things can go wrong when you multi boot with Windows and do this over a change of Summer/Winter time :frowning:

10

On 2013-03-26 05:46, eng-int wrote:
>
> paulparker;2541000 Wrote:
>>
>> Does the Gnome desktop clock adjust from system time to local time ?
>
> Probably displays according to the desktop user’s configuration. (I
> only use KDE.)

Yes, the desktop has to be ignored for clock issues.

> Is this a system time or logfile format question?

Yes, I was going to ask the same.

Maybe the clock is as it should be, but you want the timestamps in the
logs done differently.

> What do you get with this?
>
> Code:
> --------------------
>
> :~ # echo -e "
hwclock:" ;hwclock -r ;echo -e "
date:" ;date ;echo -e "
ntpd status:" ;systemctl status ntpd.service
>
> --------------------

I would also like to see the output of:


su -
hwclock --debug
date
grep -i HWCLOCK /etc/sysconfig/clock

in a terminal.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

11

On 2013-03-26 19:36, Carlos E. R. wrote:
> I would also like to see the output of:
>
>


>  su -
>  hwclock --debug
>  date
>  grep -i HWCLOCK /etc/sysconfig/clock
>

in a terminal.

Forgot one:


cat /etc/adjtime

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

12 

linux-bnn6:~ # echo -e "
 hwclock:" ;hwclock -r ;echo -e "
 date:" ;date ;echo -e "
 ntpd status:" ;systemctl status ntpd.service  

 hwclock:
Fri Mar 29 23:47:07 2013  -0.344604 seconds

 date:
Thu Mar 28 23:47:07 EST 2013

 ntpd status:
ntp.service - LSB: Network time protocol daemon (ntpd)
      Loaded: loaded (/etc/init.d/ntp)
      Active: active (running) since Fri, 2013-03-29 15:13:03 EST
     Process: 3017 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS)
      CGroup: name=systemd:/system/ntp.service
          └ 3083 /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -i /var/lib/ntp -c /etc/ntp.conf

Mar 29 15:13:03 linux-bnn6 ntpd[3083]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Mar 29 15:13:03 linux-bnn6 ntpd[3083]: Listen and drop on 1 v6wildcard :: UDP 123
Mar 29 15:13:03 linux-bnn6 ntpd[3083]: Listen normally on 2 lo 127.0.0.1 UDP 123
Mar 29 15:13:03 linux-bnn6 ntpd[3083]: Listen normally on 3 eth0 10.0.0.2 UDP 123
Mar 29 15:13:03 linux-bnn6 ntpd[3083]: Listen normally on 4 lo ::1 UDP 123
Mar 29 15:13:03 linux-bnn6 ntpd[3083]: Listen normally on 5 eth0 fe80::52e5:49ff:fe9d:3c85 UDP 123
Mar 29 15:13:03 linux-bnn6 ntpd[3083]: peers refreshed
Mar 29 15:13:03 linux-bnn6 ntpd[3083]: Listening on routing socket on fd #22 for interface updates
Mar 29 15:13:03 linux-bnn6 ntp[3017]: Starting network time protocol daemon (NTPD)..done
Mar 29 15:13:03 linux-bnn6 systemd[1]: Started LSB: Network time protocol daemon (ntpd).
linux-bnn6:~ # 




linux-bnn6:~ # touch file
linux-bnn6:~ # ls -l file
-rw-r--r-- 1 root root 0 Mar 28 23:50 file
linux-bnn6:~ # TZ=UTC ls -l file
-rw-r--r-- 1 root root 0 Mar 28 12:50 file
linux-bnn6:~ # TZ='Australia/Brisbane' ls -l file
-rw-r--r-- 1 root root 0 Mar 28 22:50 file
linux-bnn6:~ # 




linux-bnn6:~ # hwclock --debug
hwclock from util-linux 2.21.2
Using /dev interface to clock.
Last drift adjustment done at 0 seconds after 1969
Last calibration done at 0 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2013/03/29 12:52:44
Hw clock time : 2013/03/29 12:52:44 = 1364561564 seconds since 1969
Fri Mar 29 23:52:44 2013  -0.453572 seconds
linux-bnn6:~ # date
Thu Mar 28 23:52:44 EST 2013
linux-bnn6:~ # grep -i HWCLOCK /etc/sysconfig/clock
# forwarded to /etc/adjtime, the file used by hwclock(8),
## Description:        Do or do not not run hwclock(8)
USE_HWCLOCK="yes"
linux-bnn6:~ #

(long day, away, now need be off for some sleep )

13

Well if your bit of the globe is spinning backwards, you are bound to be tired.

If you are in NSW shouldnt your local time be EDT – or are you like me and do not bother with changing the clocks, just to change them back a few months later (“Daylight Saving” is just smoke and mirrors, I keep GMT all year)

Your system thinks that the hardware clock is set to UTC, but it is actually set to EST+24h.

The log extract that you showed us seemed to be from the boot sequence. Before the network is up, and ntpd started the only time available is from the HWC.

If you are dual-booting with MS Windows or DOS You should find out how to set that to use UTC rather than local time for the HWC.
The 24 hours is reminiscent of MS’s famous leap year fiascos
Otherwise the BIOS clock has been set manually and incorrectly.

When a Linux machine iiiis powered down (I am not sure what happens with the newfangled systemd and “quick boot” or hibernation) it should write the system (UTC) time to the hardware clock… If there is no controlled power down then the HWC does not get it’s time fixed.

If the ntpd is running and synchronised to a good external server you can set the HWC to UTC manually with


:~ # hwclock --systohc
14

On 2013-03-28 14:06, paulparker wrote:

> Code:
> --------------------
>
> linux-bnn6:~ # hwclock --debug
> hwclock from util-linux 2.21.2
> Using /dev interface to clock.
> Last drift adjustment done at 0 seconds after 1969
> Last calibration done at 0 seconds after 1969
> Hardware clock is on UTC time
> Assuming hardware clock is kept in UTC time.
> Waiting for clock tick…
> …got clock tick
> Time read from Hardware Clock: 2013/03/29 12:52:44
> Hw clock time : 2013/03/29 12:52:44 = 1364561564 seconds since 1969
> Fri Mar 29 23:52:44 2013 -0.453572 seconds
> linux-bnn6:~ # date
> Thu Mar 28 23:52:44 EST 2013
> linux-bnn6:~ # grep -i HWCLOCK /etc/sysconfig/clock
> # forwarded to /etc/adjtime, the file used by hwclock(8),
> ## Description: Do or do not not run hwclock(8)
> USE_HWCLOCK=“yes”
> linux-bnn6:~ #
>
>
> --------------------

Yes, the cmos clock is 1 day off compared to the system clock. In the
grep from “/etc/sysconfig/clock” I miss one entry compared to mine (on
12.1):


cer@Telcontar:~> grep -i HWCLOCK /etc/sysconfig/clock
HWCLOCK="-u"
cer@Telcontar:~>

I’m not sure how important that is in 12.3.
I also miss the contents of “/etc/adjtime”, and if it does not exist
that could be also part of the problem.

Another interesting output would be the output of


grep -i timezone /etc/sysconfig/clock
locale

Then we can think what to do to correct it all.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

15

Date and Time settings

No change over past several hours:


linux-bnn6:~ # hwclock --systohc
linux-bnn6:~ #

Light bulb in the mind moment, when reading these words from eng-int created understanding: our system thinks that the hardware clock is set to UTC, but it is actually set to EST+24h.

Suspect this a common mis-understanding, during installation and later.

**So needed change bios date and time settings where access bios at start of boot pre-GRUB to manually adjust computer’s bios date and time setting to UTC. **

Re-booted, found bios showing my LOCAL date and time, not the UTC date and time.

Adjusted computer’s bios date and time setting to UTC.

Re-start to be sure settings OK.

OK appears to starts in bios of UTC time, then be adjusted by ntpd to show local time.


linux-bnn6:~ # grep -i 'ntpd' /var/log/messages

---deleted---

2013-03-28T23:09:32.314946+00:00 linux-bnn6 systemd[1]: Starting LSB: Network time protocol daemon (ntpd)...
2013-03-28T23:09:32.342928+00:00 linux-bnn6 ntpd[3089]: ntpd 4.2.6p5@1.2349-o Fri Mar  1 11:32:34 UTC 2013 (1)
2013-03-28T23:09:32.343668+00:00 linux-bnn6 ntpd[3090]: proto: precision = 0.120 usec
2013-03-28T23:09:32.344266+00:00 linux-bnn6 ntpd[3090]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
2013-03-28T23:09:32.345040+00:00 linux-bnn6 ntp[3034]: Starting network time protocol daemon (NTPD)..done
2013-03-28T23:09:32.352073+00:00 linux-bnn6 systemd[1]: Started LSB: Network time protocol daemon (ntpd).
2013-03-28T23:09:32.353943+00:00 linux-bnn6 ntpd[3090]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
2013-03-28T23:09:32.353945+00:00 linux-bnn6 ntpd[3090]: Listen and drop on 1 v6wildcard :: UDP 123
2013-03-28T23:09:32.353948+00:00 linux-bnn6 ntpd[3090]: Listen normally on 2 lo 127.0.0.1 UDP 123
2013-03-28T23:09:32.356235+00:00 linux-bnn6 ntpd[3090]: Listen normally on 3 eth0 10.0.0.2 UDP 123
2013-03-28T23:09:32.356252+00:00 linux-bnn6 ntpd[3090]: Listen normally on 4 lo ::1 UDP 123
2013-03-28T23:09:32.356255+00:00 linux-bnn6 ntpd[3090]: Listen normally on 5 eth0 fe80::52e5:49ff:fe9d:3c85 UDP 123
2013-03-28T23:09:32.356257+00:00 linux-bnn6 ntpd[3090]: peers refreshed
2013-03-28T23:09:32.356259+00:00 linux-bnn6 ntpd[3090]: Listening on routing socket on fd #22 for interface updates
2013-03-29T10:19:34.491235+11:00 linux-bnn6 systemd[1]: Starting LSB: Network time protocol daemon (ntpd)...
2013-03-29T10:19:34.504197+11:00 linux-bnn6 ntpd[3000]: ntpd 4.2.6p5@1.2349-o Fri Mar  1 11:32:34 UTC 2013 (1)
2013-03-29T10:19:34.505008+11:00 linux-bnn6 ntpd[3003]: proto: precision = 0.107 usec
2013-03-29T10:19:34.505574+11:00 linux-bnn6 ntpd[3003]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
2013-03-29T10:19:34.505855+11:00 linux-bnn6 ntpd[3003]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
2013-03-29T10:19:34.510208+11:00 linux-bnn6 ntpd[3003]: Listen and drop on 1 v6wildcard :: UDP 123
2013-03-29T10:19:34.510229+11:00 linux-bnn6 ntpd[3003]: Listen normally on 2 lo 127.0.0.1 UDP 123
2013-03-29T10:19:34.510231+11:00 linux-bnn6 ntpd[3003]: Listen normally on 3 eth0 10.0.0.2 UDP 123
2013-03-29T10:19:34.510235+11:00 linux-bnn6 ntpd[3003]: Listen normally on 4 lo ::1 UDP 123
2013-03-29T10:19:34.510265+11:00 linux-bnn6 ntpd[3003]: Listen normally on 5 eth0 fe80::52e5:49ff:fe9d:3c85 UDP 123
2013-03-29T10:19:34.510546+11:00 linux-bnn6 ntpd[3003]: peers refreshed
2013-03-29T10:19:34.510723+11:00 linux-bnn6 ntpd[3003]: Listening on routing socket on fd #22 for interface updates
2013-03-29T10:19:34.519197+11:00 linux-bnn6 ntp[2961]: Starting network time protocol daemon (NTPD)..done
2013-03-29T10:19:34.519385+11:00 linux-bnn6 systemd[1]: Started LSB: Network time protocol daemon (ntpd).
linux-bnn6:~ # 




linux-bnn6:~ # grep -i timezone /etc/sysconfig/clock
## Description:        Information about your timezone and time
# Timezone (e.g. CET or Asia/Tokyo). The value should correspond
TIMEZONE="Australia/Sydney"
DEFAULT_TIMEZONE="US/Eastern"
linux-bnn6:~ # locale
LANG=POSIX
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
linux-bnn6:~ #

.

16

No! If Linux could cope with your BIOS and ACPI, the "hwclock --systohc" should have done that. You can read /etc/sysconfig/clock and check that it seems reasonable.

linux-bnn6:~ # grep -i timezone /etc/sysconfig/clock

Description: Information about your timezone and time

Timezone (e.g. CET or Asia/Tokyo). The value should correspond

TIMEZONE=“Australia/Sydney”
DEFAULT_TIMEZONE=“US/Eastern”

Australian EST seems to have been confused with US Eastern time.
YaST > System > Date and Time
Select e.g. Australia > New South Wales (Sydney), Hardware Clock Set to UTC, OK

linux-bnn6:~ # locale
LANG=POSIX
LC_CTYPE=en_US.UTF-8
LC_TIME=“POSIX”
…

You are going to default to weird US paper sizes and date formats, etc.
YaST > System > Language
Primary Language select English (UK)

[Details] > Detailed Locale Setting select en_AU

The old "rcntp status" provides different information to “systemctl status ntpd.service”, in future I shall use both.

17

On 2013-03-29 03:26, eng-int wrote:
> No! If Linux could cope with your BIOS and ACPI, the -“hwclock
> --systohc-” should have done that. You can read -/etc/sysconfig/clock-
> and check that it seems reasonable.

It needs that the setting in “/etc/adjtime” be correct. The last line in
the file that says “UTC” or “LOCAL”. If the file does not exist (there
was a bug in 12.2, the file was not always created) then hwclock can
make the wrong assumption and set the clock wrong.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

18 

linux-bnn6:~ # rcntp status
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*ntp1.warwicknet 195.66.241.3     2 u  139  512  377  323.289   -1.683   1.091

Checking for network time protocol daemon (NTPD):                                                                                                                                                       running
ntp.service - LSB: Network time protocol daemon (ntpd)
      Loaded: loaded (/etc/init.d/ntp)
      Active: active (running) since Fri, 2013-03-29 11:37:17 EST; 2h 52min ago
     Process: 3019 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS)
      CGroup: name=systemd:/system/ntp.service
          └ 3081 /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -i /var/lib/ntp -c /etc/ntp.conf

Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listen and drop on 1 v6wildcard :: UDP 123
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listen normally on 2 lo 127.0.0.1 UDP 123
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listen normally on 3 eth0 10.0.0.2 UDP 123
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listen normally on 4 lo ::1 UDP 123
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listen normally on 5 eth0 fe80::52e5:49ff:fe9d:3c85 UDP 123
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: peers refreshed
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listening on routing socket on fd #22 for interface updates
Mar 29 11:37:17 linux-bnn6 ntp[3019]: Starting network time protocol daemon (NTPD)..done
Mar 29 11:37:17 linux-bnn6 systemd[1]: Started LSB: Network time protocol daemon (ntpd).
linux-bnn6:~ # systemctl status ntpd.service
ntp.service - LSB: Network time protocol daemon (ntpd)
      Loaded: loaded (/etc/init.d/ntp)
      Active: active (running) since Fri, 2013-03-29 11:37:17 EST; 2h 52min ago
     Process: 3019 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS)
      CGroup: name=systemd:/system/ntp.service
          └ 3081 /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -i /var/lib/ntp -c /etc/ntp.conf

Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listen and drop on 1 v6wildcard :: UDP 123
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listen normally on 2 lo 127.0.0.1 UDP 123
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listen normally on 3 eth0 10.0.0.2 UDP 123
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listen normally on 4 lo ::1 UDP 123
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listen normally on 5 eth0 fe80::52e5:49ff:fe9d:3c85 UDP 123
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: peers refreshed
Mar 29 11:37:17 linux-bnn6 ntpd[3081]: Listening on routing socket on fd #22 for interface updates
Mar 29 11:37:17 linux-bnn6 ntp[3019]: Starting network time protocol daemon (NTPD)..done
Mar 29 11:37:17 linux-bnn6 systemd[1]: Started LSB: Network time protocol daemon (ntpd).
linux-bnn6:~ #

YaST > System > Language

Primary Language SET= English (UK) then when select Australian for secondary it resets to Australian as Primary, even though did not offer this as a choice.

so now set as :

Primary Language = en-AU
Secondary Language = English (UK)

[opened box title: Language Details]

        Locale Settings for user root:    YES 
                   Use UTF-8 encoding:    YES 
        Detailed Locale Settings:    en_AU  


linux-bnn6:~ # cat  /etc/adjtime
0.000000 1364533081 0.000000
1364533081
UTC
linux-bnn6:~ # grep -i timezone /etc/sysconfig/clock
## Description:        Information about your timezone and time
# Timezone (e.g. CET or Asia/Tokyo). The value should correspond
TIMEZONE="Australia/Sydney"
DEFAULT_TIMEZONE="US/Eastern"
linux-bnn6:~ #

IF the system default date and time is UTC, should clock default_TimeZone = UTC ?

Will do shutdown, restart, then see if anything above has changed.

.

19

Thanks eng-int :slight_smile:

Seems OK now except for DEFAULT_TIMEZONE=“US/Eastern” .

Now allow a few days for changes to appear.

20

On 2013-03-29 07:36, paulparker wrote:
>
> Thanks eng-int :slight_smile:
>
> Seems OK now except for DEFAULT_TIMEZONE=“US/Eastern” .

Edit it yourself.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)