SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
date -s [time string] <-------set time
hwclock -w <-------set hardware clock to system time
your current time/date and timezone settings as reported by date
the output from hwclock --show
the output from zcat /proc/config.gz | grep CONFIG_RTC_[SH]
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.
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
EDIT: I don't understand this "grep" thing. What does it do?
Last edited by GiveMeSomeSlackware; 11-18-2013 at 10:43 AM.
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
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.