I am trying to sync with the US time server. Every time I do, it will result in a time that is way off. If it's 7 PM, it would be set to 1 AM of the next day.

Tour time zone settings are probably incorrect. What does date say about your time zone? If it doesn't match your physical location, run timeconfig to select a different time zone.

Are you using ntpd to synchronize the clock? Which time server(s) are you using?

1 members found this post helpful.

Linux systems are commonly set to UTC (Greenwich Mean) time and use the timezone setting to convert that to local time for display purposes. In general, servers are commonly set to UTC time for world-wide time compatibility and Linux is descended from serverland.

This article will tell you more about how time works on Slackware.

It took me quite a while (like years), but I finally figured out to my own satisfaction how to set time in a way that works for me. The only effective way to do it thoroughly is as root, from the command line.

I will use the date command to set the time I desire, then the hwclock (hardwareclock) command to set the hardware clock to the system time.

I had before reading this, i had to manually reset it. Now doing...

...in console as a normal user gives me the right time.

Yes, I am using ntpd. The server is, us.pool.ntp.org. Still though it never works right.

In case if this matters, I generally set my hardware clock to localtime, not UTC.

EDIT: From Sunday night to noon Friday, I am unable to access such servers (and several other servers/websites) for some weird reason.

Same problem, in 14.1 have some problem with time.

About a decade ago I got tired of dorking around with ntp's capriciousness and wrote a little script:

http://ciar.org/ttk/public/rsetdate

It gets the clock close enough for personal use (within a second), so I just stick it in /etc/cron.daily and forget about it. It's not a good solution, just a convenient one.

Are you using KDE as your desktop environment? If so you need to set the correct timezone in KDE as well. Right click on the digital clock in the task bar then select "Adjust Date and Time"

Have a read of this thread as it sounds like it might be the problem :-

http://www.linuxquestions.org/questi...me-4175477525/

the settings in kde are correct to. I still don't get why I am having so many problems with it.

Could you post the following:

1. your current time/date and timezone settings as reported by date
2. the output from hwclock --show
3. the output from zcat /proc/config.gz | grep CONFIG_RTC_[SH]
4. the contents of /etc/ntp.conf (perhaps filtered through grep -v "^#.*" for brevity)

FWIW, I'm using ntpd on several Slackware systems with the hardware clock set to local time, and apart from some issues with the RTC options in recent kernels, I haven't had any problems at all.

bash-4.2# date
Mon Nov 18 09:40:29 CST 2013
bash-4.2# hwclock --show
Mon 18 Nov 2013 09:40:33 AM CST -0.626721 seconds
bash-4.2# zcat /proc/config.gz | grep CONFIG_RTC_[SH]
# CONFIG_RTC_HCTOSYS is not set
# CONFIG_RTC_SYSTOHC is not set
bash-4.2#


EDIT: I don't understand this "grep" thing. What does it do?

According to the official source, both your system and hardware clocks are showing the correct time for the CST time zone.
It just reads data from standard input (usually piped from some other program), and displays lines matching the search criteria (or lines not matching the search criteria, if you use the "-v" switch).

1 members found this post helpful.

My clock is off all the time too. right now I am 24 minutes too fast. I tried the steps found here are not helping. Anyone come up with a solution please do post here. Thanks

/etc/rc.d/rc.ntpd stop (if it's running)
timeconfig
ntpdate pool.ntp.org
hwclock --localtime --systohc or hwclock --utc --systohc (depending on what you chose in timeconfig)

/etc/rc.d/rc.ntpd start (if you want)

It's possible existing processes/daemons may still be using the old timezone, stop/start them or if in doubt reboot.

1 members found this post helpful.

There is no one solution. What is the output of `ntpq -p -c rv`? Should you launch ntpd with the -g flag (allow first adjustment to be large), does the time get set correctly and then drift later? More questions may follow.