SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
you have to update the /etc/ntp.conf with the correct NTP Server or else it won't get any updates at all
Yes i have done that, I have the server from my University.
Until the change in hour was working well.
I ran ntpq -p and see connected to peers.
Now says
To set your local time zone run, as root, 'timeconfig'.
To get ntp to run automatically, /etc/rc.d/rc.ntpd needs to be executable. Use 'ntpd -q' for one off time updates.
A properly configured ntp setup will handle daylight saving changes. Perhaps you could post your /etc/ntp.conf file.
# Sample /etc/ntp.conf: Configuration file for ntpd.
#
# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available. The
# default stratum is usually 3, but in this case we elect to use stratum
# 0. Since the server line does not have the prefer keyword, this driver
# is never used for synchronization, unless no other other
# synchronization source is available. In case the local host is
# controlled by some external source, such as an external oscillator or
# another protocol, the prefer keyword would cause the local host to
# disregard all other synchronization sources, unless the kernel
# modifications are in use and declare an unsynchronized condition.
#
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
#server pool.ntp.org
# Portugal NTP SERVER
server 3.pt.pool.ntp.org
server 3.europe.pool.ntp.org
server 2.europe.pool.ntp.org
# UA NTP SERVER
server 193.136.172.21
server 193.136.172.20
#
# Drift file. Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
#
driftfile /etc/ntp/drift
multicastclient # listen on default 224.0.1.1
broadcastdelay 0.008
#
# Keys file. If you want to diddle your server at run time, make a
# keys file (mode 600 for sure) and define the key number to be
# used for making requests.
# PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote
# systems might be able to reset your clock at will.
#
#keys /etc/ntp/keys
#trustedkey 65535
#requestkey 65535
#controlkey 65535
# Don't serve time or stats to anyone else by default (more secure)
restrict default noquery nomodify
# Trust ourselves. :-)
restrict 127.0.0.1
willysr brought up a good point about configuring ntpd. Here's what my configuration (/etc/ntp.conf) looks like:
Code:
restrict default notrust nomodify noquery
restrict 172.16.0.0 mask 255.255.255.0 nomodify
fudge 127.127.1.0 stratum 10
server pool.ntp.org iburst
server pool.ntp.org iburst
server pool.ntp.org iburst
server pool.ntp.org iburst
server 127.127.1.0
restrict pool.ntp.org nomodify
restrict pool.ntp.org nomodify
restrict pool.ntp.org nomodify
restrict pool.ntp.org nomodify
restrict 127.0.0.1
driftfile /etc/ntp/ntp.drift
logfile /var/log/ntp.log
This code runs on my gateway computer running Slackware 13.1. The second "restrict" line allows only the computers in my home network to access the NTP daemon on the gateway. Other than the two restrict lines, you should be able to use that configuration since there are now pool servers that are farmed out as needed to clients.
Are you by any chance dual booting into Windows? AFAIK, Windows stores localtime in system clock, while Linux can be configured to store localtime or UTC. What's inside /etc/hardwareclock file?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.