You are not logged in.
Pages: 1
Hi, a little help here, I currently have a strange problem with my clock, EVERYTIME i boot the clock in wrong, and if I set it to the correct time, it changes ALL of my other OS's clocks, its very weird, for example lets say Arch boots up and the clock says 3:14pm, but it is 8:26pm, If I change the time to 8:26 pm, all my other OS's (Windows and ubuntu) change time to a different one.
This shouldnt be the case cause I THINK time is operating system independent, right? I mean a change of time in one Os shouldnt have to change the other OS time.
Any info on this will be appreciated
cheers
Last edited by 655321 (2010-07-19 08:31:49)
Linux user #498977
With microsoft you get windows and gates, with linux you get the whole house!
My Blog about ArchLinux and other stuff
Offline
There is hardware time and system (software) time. It's in the wiki.
Offline
I just use NTPD everywhere so I never have to worry about these kind of things. Also it's kind of nice to know you have exactly the correct time on your machine (well, almost exactly).
Offline
@ splittercode
It may be good idea, but first OP has to set the correct time - NTPD makes sure it is kept correct, but it won't fix a ~5hrs skew.
Offline
This shouldnt be the case cause I THINK time is operating system independent, right? I mean a change of time in one Os shouldnt have to change the other OS time.
One way around this logical block is to think how the OS keeps track of time between power downs.
aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies
Offline
also, as you are booting several OS's make sure your /etc/rc.conf, your HARDWARECLOCK is set to "localtime" instead of UTC
from the wiki "Specifies whether the hardware clock, which is synchronized on boot and on shutdown, stores UTC time, or localtime. UTC makes sense because it greatly simplifies changing timezones and daylight savings time. localtime is necessary if you dual boot with an operating system such as Windows, that only stores localtime to the hardware clock."
http://wiki.archlinux.org/index.php/Beg … ON_section
Last edited by scarletxfi (2010-07-17 09:34:44)
Offline
@ splittercode
It may be good idea, but first OP has to set the correct time - NTPD makes sure it is kept correct, but it won't fix a ~5hrs skew.
ntpd -s will help here. I have the following aliased for when I boot *ahem* windows:
ntpd -d -s && sudo hwclock --systohc
Offline
-s statsdir
Specify the directory path for files created by the statistics facility.
I don't think I get it, what does the '-s' flag do?
Offline
If you use openntpd:
-s Set the time immediately at startup. Allows for a large time
correction, eliminating the need to run rdate(8).
Offline
Ah, thanks anonymous_user.
Offline
Just reporting that problem was indeed on my rc.conf, now clock doesnt change BUT, thanks to all
problem solved
Linux user #498977
With microsoft you get windows and gates, with linux you get the whole house!
My Blog about ArchLinux and other stuff
Offline
ahhhh, thanks, I had that same problem and now it' FIXED!!!!!
Offline
Pages: 1