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.
Using the latest glibc-zoneinfo (glibc-zoneinfo-2.5-noarch-5_slack12.0.tgz)
but the clock is still on DST. ntpdate syncs with no errors, but I'm still an hour ahead. What am I missing?
hmm, mine was running a hour slow for a while after upgrading to -current. It cleared up by itself, after resetting timezone settings (which were correct) and several syncs to pool.ntp.org and a couple of reboots into XP and back. In other words I have no idea what the cause is, but had similar problems myself.
Last edited by Eternal_Newbie; 11-04-2007 at 10:25 AM.
Reason: spelling
combination of date, hwclock and ntp worked for me
Hi.
Both the clock on my x86 slackware 12 box and the clock on my ppc slackintosh 12 box adjusted themselves to the time change accordingly, the way they were supposed to. I only installed slack this past month, and I do remember that I had to mess with the clocks initially, and this is what I did, all from console:
I. I set the system date manually, so it wouldn't be too far off when trying to sync later with ntp. To set the date to November 4 at 9:09am, I typed "sudo date 11040909"
II. I set my timezone by creating a symbolic link for localtime in /etc. I typed: "sudo ln -s /usr/share/zoneinfo/US/Pacific /etc/localtime" and this did the trick. I had to erase the prior localtime file that was there, which seemed to be a link to a copy of the zone info, and so I removed the old localtime, replaced it with the symbolic link I just described.
III. I checked my ntp configuration at /etc/ntp.conf, and made sure that pool.ntp.org was listed as a server, and then I enabled ntpd, by typing "sudo chmod 0775 /etc/rc.d/rc.ntpd" and then typing "sudo /etc/rc.d/rc.ntpd start" -- and the clock then syncs automatically
IV. Then, once the system clock is synced with the pool.ntp.org servers, I set the real time clock to the system time by typing: "sudo hwclock --systohc"
And this worked for me... the clocks changed time according. However, I am a total linux noob, and was just guessing, tinkering, and trial and erroring, so I don't know if these ways constitute a "best practice."
Does it have to do with UTC vs localtime? Or maybe it has to do with upgraded installations? Because I have two slack 12 systems. One changed correctly the other did not. The one that did not was on localtime because it has XP as well.
Somehow my time changed correctly this morning on my Slackware 12 machine, and I don't even have it setup for internet-time update. Beats me how it happened. It's an older computer so I doubt it is built into my bios, especially since daylight saving time shifted a few years back. How did Slackware know to change my time? Probably a silly question I know.
I had a similar experience to digger95. The Orage clock in xfce didn't update to daylight savings until a few days after the event. One of my slightly computer-challenged friends asked me how the hardware clock manages to stay in time when the computer is turned off, and I had to admit I have no idea.
asked me how the hardware clock manages to stay in time when the computer is turned off, and I had to admit I have no idea.
Your computer's motherboard has a small battery which 'is used to keep the NVRAM "refreshed" for many years. Therefore, a failing battery on a motherboard will produce the symptoms of a computer that cannot determine the correct date and time, nor remember what hardware configuration the user has selected. The BIOS itself is unaffected by the status of the battery.' (http://en.wikipedia.org/wiki/Motherboard).
Both of my Slackware 12 machines, a desktop and a laptop, failed to change the time correctly. I had to manually change it with date --set and hwclock --systohc. The only possible cause I found is that /etc/localtime wasn't a symlink to something in /usr/share/zoneinfo. It worked earlier this year, before upgrading glibc-zoneinfo, when /etc/localtime was a symlink.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.