LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 11-04-2007, 10:00 AM   #1
2Gnu
Senior Member
 
Registered: Jan 2002
Location: Southern California
Distribution: Slackware 13.1
Posts: 1,872

Rep: Reputation: 48
Time Change ... didn't


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?

Thanks.
 
Old 11-04-2007, 10:24 AM   #2
Eternal_Newbie
Member
 
Registered: Jun 2005
Location: The Pudding Isles
Distribution: Slackware 13.37
Posts: 550

Rep: Reputation: 49
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
 
Old 11-04-2007, 11:26 AM   #3
globaltree
Member
 
Registered: Oct 2007
Location: Oregon
Distribution: Slackware 12.2
Posts: 65

Rep: Reputation: 18
Cool 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."
 
Old 11-04-2007, 11:51 AM   #4
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,295

Rep: Reputation: Disabled
My slack 11 box changed properly, my slack 12 box didn't.

Brian
 
Old 11-04-2007, 01:21 PM   #5
the3dfxdude
Member
 
Registered: May 2007
Posts: 234

Rep: Reputation: 32
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.
 
Old 11-04-2007, 02:46 PM   #6
2Gnu
Senior Member
 
Registered: Jan 2002
Location: Southern California
Distribution: Slackware 13.1
Posts: 1,872

Original Poster
Rep: Reputation: 48
Fixed.

On closer inspection, it was the XFCE4 clock was off. The command "date" shows the correct time.

The Orage clock was set to Z 7 - 7 hour GMT offset. Set it to Z 8.
 
Old 11-04-2007, 03:05 PM   #7
digger95
Member
 
Registered: Oct 2007
Location: Indiana, PA
Distribution: Slackware 12.1
Posts: 256

Rep: Reputation: 31
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.
 
Old 11-04-2007, 05:49 PM   #8
samwise17
Member
 
Registered: Jul 2007
Location: Sydney
Distribution: Arch,Slackware,Puppy
Posts: 87

Rep: Reputation: 15
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.
 
Old 11-04-2007, 06:00 PM   #9
msantinho
Member
 
Registered: Oct 2005
Location: Lisbon
Distribution: Slackware
Posts: 51

Rep: Reputation: 15
Quote:
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).
 
Old 11-07-2007, 07:01 AM   #10
Eternal_Newbie
Member
 
Registered: Jun 2005
Location: The Pudding Isles
Distribution: Slackware 13.37
Posts: 550

Rep: Reputation: 49
Could I just confirm that everyone else who had a problem also had their hardware clock set to local time, not UCT?
 
Old 11-07-2007, 10:42 AM   #11
mattydee
Member
 
Registered: Dec 2006
Location: Vancouver, BC
Distribution: Slackware sans KDE4 (Gnome Slackbuild)
Posts: 454

Rep: Reputation: 35
Quote:
Originally Posted by Eternal_Newbie View Post
Could I just confirm that everyone else who had a problem also had their hardware clock set to local time, not UCT?
I had a similar problem and my clock is set to localtime (because of windows).
 
Old 11-07-2007, 02:47 PM   #12
dracolich
Senior Member
 
Registered: Jul 2005
Location: Va Beach
Distribution: Slackware
Posts: 1,159

Rep: Reputation: 47
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.
 
  


Reply

Tags
date, hwclock, linux, ntp, slackware, time, timezone


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Is it time for change? Larry Webb LQ Suggestions & Feedback 2 10-06-2007 05:48 AM
Various clock issues: Clock shows wrong time only in Knoppmyth, & CMOS time change ? davidbix General 1 04-05-2006 09:58 PM
Need ACCESS to change files! Every time I try to change a setting,"Permission Denied" Balarabay1 Suse/Novell 2 03-06-2006 09:54 AM
Daytime Saving time. Cannot change time arubin Linux - General 9 11-06-2004 04:37 PM
Change time? fedivh Linux - General 12 04-21-2004 12:38 PM


All times are GMT -5. The time now is 10:22 AM.

Main Menu
 
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: @linuxquestions
Open Source Consulting | Domain Registration