This discussion is archived
8068 Views 6 Replies Latest reply: Dec 1, 2008 8:43 PM by Jason Anthony
Currently Being ModeratedOct 8, 2008 8:26 AM (in response to Spencer Filichia)A wild stab:
In the Date and Time selections, have you checked "Set Date and Time automatically"?
Whatever setting you have for that option, try the other one. Then restart, and reset the PRAM
Currently Being ModeratedOct 8, 2008 8:40 PM (in response to Eustace Mendis)I tried resetting the PRAM and that didn't work. Also tried changing the settings on the clock from manual to automatic an that does nothing as well. When I set it to set time automatically it thinks the timezone is GMT and sets the clock 7 hours in the future.
Any other ideas? This one is really a stumper.PowerBook G4 17", Mac OS X (10.4.11)
Currently Being ModeratedOct 13, 2008 9:42 AM (in response to Spencer Filichia)If you copied everything onto the new drive, the /usr/share/zoneinfo/ directory maybe corrupt. You can check the file sizes by either using the Terminal.app or the Go To Folder menu item in the Go menu in the Finder. Make sure all the files have a file size > 0. The date & time preferences panel will fail to change to a time zone that doesn't have a valid file in the /usr/share/zoneinfo/ directory.
If you find some files with a file size of 0, try to find a valid replacement on your back up disk.
SteveMac Pro G5, Mac OS X (10.4.11)
Currently Being ModeratedNov 9, 2008 10:23 AM (in response to Spencer Filichia)Solved this finally. Read this thread for the details.
After doing some more digging I seemed to have solved by own problem. Thought I'd share it just in case someone else has the problem.
The problem ended up being that my "localtime" file was locked. When originally trying to solve this problem there was a solution suggested about the "localtime" file being corrupt. That was found on this post.
A post by barnamink read:
I had this problem, and after unsuccessful attempts by Apple's support to diagnose it, I figured it out myself. The problem was with the /etc/localtime file. It was a directory, instead of a symlink. I think Tiger (which is just what I migrated from) used to have it as a directory, whereas Leopard changed it to a symlink. Long story short, if you erase / rename your /etc/localtime, and then set the timezone, it will start working.
You will need to enable the root user for this, so be sure you know what you're doing. But once you're root, just do a
mv localtime localtime.old
Then set the time zone again, and this time it will remember it.
I played with this but couldn't get it to stick. The "localtime" file which is really just an alias would still go back to GMT. I discovered that it should point back to my time zone which is "PST". So I found those files.
I made a new alias and named it localtime. Then I replaced the one in the /etc directory. The funny thing was that it would point back to the "pacific" file, but when I would open my date and time preferences and try to reset the time zone it changed the alias to point back to GMT which was located at usr/share/zoneinfo. So to try and stop this from happening I repeated the process of making a new alias and then locked it. It prevented it from repointing back to the GMT file, but it did not solve my problem.
Then I did the system re-install. I had forgotten about locking the file, by the way. The re-install I think fixes what ever the problem was with not being able to change timezones, but then I ran into the problem of saving the new time zone. The problem was the locked "localtime" file. I tried doing the same thing of just replacing this file, but now that it was locked I couldn't delete it or even unlock it.
I finally fixed the problem, but I may have taken the long way around to do it. I'll explain exactly what I did and then say what I think would be the quicker solution. I used the terminal to unlock the "localtime" file. I got this info from another post.
The solution was posted by Steve Gregorich and I adopted it for my problem. It boils down to this.
Open /Applications/Utilities/Terminal, and paste this text in, but DON'T press enter yet.
Make sure there is one space in front of the text and type a space after "nouchg."
Now drag the affected folder into Terminal, and press enter.
After closing Terminal, go back and do the "get info" thing again.
If that does not work, repeat the process, but put "sudo" in front of "chflags". You'll need to type your admin password in that case.
Message was edited by: Steve Gregorich
I had to use the "Sudo" command and so this is what I typed.
sudo chflags nouchg /private/etc/localtime
That did indeed unlock the file. I should have tried my clock preferences at this step to see if they saved, but I didn't because my mind was still on the track of replacing the file. If you try this solution, I suggest trying the preferences at this point, because I think what I did next was unnecessary. I went through the whole process I described earlier about making a new alias and replacing he "localtime" file with the new alias. After doing that my clock now seems to work.
Sorry for anyone who reads this if I rambled and took too long to explain, but I thought clarity was important. I've been trying to solve this whole clock thing or over a month on and off and so actually finding a solution is a big deal. I hope this helps anyone else who may have this problem.
Message was edited by: Spencer FilichiaPowerBook G4 17", Mac OS X (10.4.11)
Currently Being ModeratedDec 1, 2008 8:43 PM (in response to Spencer Filichia)Ok, Had to respond to this because this is the wackiest thing I've ever seen.
Had the same problem, resulting from migrating from Tiger to Leopard.
What worked for me was unlocking the /private/etc/localtime folder and then removing it (mv localtime localtim.old). After I renamed the folder, I went to set the timezone in preferences and it sticks. Just unlocking the folder and then going to preferences didn't work.
Glad it caught it now, this machine is going be a file server and that would have caused me some major headaches.
Thanks for posting your tips.PowerMac Dual G5 1.8 GHZ, Mac OS X (10.5.5)