Date and time settings after erroneously saying hardware clock was set to local time
 

Hi,

During the Slackware set up process I chose the option that my hardware clock was set to local time, as I was unsure as to whether hardware clock was set to local or UTC time. Running `date` in a TTY terminal while in the Slackware live session returned the UTC time, so I'm now suspecting the hardware clock was actually set to UTC time. How do I undo this unwise decision of mine to say it was set to local time, when it was probably UTC time?

Presently my Slackware install is reporting the time in my timezone to be 5:30 AM 25 July 2018, when it's 3:30 pm 25 July 2018. I looked at the date and time setting of my KDE system and it said it was set to my local time (AEST, Australia/Brisbane). This is another reason why I suspect my selection in the setup program was erroneous.

Thanks for your time,
Brenton

just run (as root)

Thanks, I just followed your advice, but unfortunately everything is still returning the erroneous time. So I'm guessing a reboot is required, which I will do now.

OK then, I'm afraid the problem is persisting despite the reboot. If I run `date` I get:

when it should return:

as that is the correct time. Any ideas what I need to do? If it is relevant I do have rc.ntpd running on boot.

maybe it's a misconfiguration of ntpd that is causing that.

if you do an
and you run (still as root)
what does the date command outputs after that?

Made no difference, I'm afraid, still reporting it's almost 7 AM.

are you sure you stopped ntpd before doing that?

what does the commands
say?

I didn't stop it, as I didn't know I was meant to (I think you added that ntpd stopping command to your previous comment after I had originally read it and acted on its original instructions), but I just did and repeated your previous command (the sntp one) and the same result occurred. Your latest command returns:

.

when you have stopped ntpd, can you please post also the output of

Here is the output:

when you run timeconfig the second time, at the beginning of the topic, you have set your clock to localtime and not UTC, right?
this unfortunately is my last guess.

well, I actually have another last one, based on the last line of that output: try also to use sntp with the -S option
and post the output.

Due to the problem I thought I had to set it to UTC, as localtime was the setting when I first noticed this problem.

Your sntp command returns:

with the UTC hardware clock setting, however, I get:

(which seems the same). Aha! Running:

with localtime as the hardware clock setting, has fixed the problem, thanks!

that confused me, because in the first post I thought you said that you wanted to do the opposite. :)
please mark the thread as solved.