You are not logged in.
Pages: 1
when i was using the livecd from opensuse, i changed the clock to the correct time (using the kde clock adjuster). when i got back into arch, my clock was wrong. i tried a few things (switching back and forth from UTC to localtime, sudo -K, whatever...). finally, i got the stupidly simple idea of going back into suse and reforking up the clock. this solved the problem.my bios clock was right even when my arch clocks were wrong (it was even wrong when doing date in the console). but, this strikes me as something that shouldn't be happening. am i wrong about that?
Offline
Is it possible that there is something going on there with TimeZones?
Offline
Is it possible that there is something going on there with TimeZones?
like what?
this was clearly the suse livecd affecting the settings of my installed arch setup.
Offline
this was clearly the suse livecd affecting the settings of my installed arch setup.
I think that would be impossible. Chances are, the clock settings in your rc.conf aren't setup properly.
Last edited by elliott (2008-06-04 08:09:31)
Offline
I am currently using openntp to maintain my clock settings. Once you install it and put openntpd in your daemons array, you should be able to reset it with a quick
/etc/rc.d/openntpd restart
Smarter than a speeding bullet
My Goodreads profile
Offline
fuscia wrote:this was clearly the suse livecd affecting the settings of my installed arch setup.
I think that would be impossible. Chances are, the clock settings in your rc.conf aren't setup properly.
why do you say that? what error are you thinking of that would cause this problem?
Last edited by fuscia (2008-06-04 13:05:46)
Offline
I second the openntpd suggestion . That settles the clock issues once and for all.
Offline
I second the openntpd suggestion . That settles the clock issues once and for all.
i fixed the clock by using the livecd to undo what it did. in my view, the issue is what caused the problem in the first place? is it an error in my rc.conf? is an arch installation affected by changes one makes to a livecd, changes that are unintended? this last one calls into question more considerations than just the clock. what if one can inadvertently affect other element's of one's arch installation that are not immediately recognized?
Offline
Wrong time zone?
/etc/rc.conf
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Moscow"
That's all it took. I inserted my time zone manually. openntpd takes care of the rest.
Offline
here's the time portion of my /etc/rc.conf
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="yes"
TIMEZONE="US/Eastern"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
this is the way it's been from the start (i live in north carolina, btw). unless there's something wrong there, i fail to see how this is an issue with my /etc/rc.conf and not a problem with using a livecd in arch. this may not be just a time zone issue. if i'm correct in thinking this is an issue with livecd's, then it could potentially affect other settings. is that not a concern?
Offline
I think Suse set your BIOS clock to local time, and Arch was expecting UTC. It isn't anything to be worried about, used to happen to me a lot when I dual booted, until I found a common ground between OS's so they handled the BIOS clock in the same way.
Last edited by elliott (2008-06-05 10:16:25)
Offline
I think Suse set your BIOS clock to local time, and Arch was expecting UTC. It isn't anything to be worried about, used to happen to me a lot when I dual booted, until I found a common ground between OS's so they handled the BIOS clock in the same way.
the bios clock was right when my arch clock was wrong.
Last edited by fuscia (2008-06-05 12:11:05)
Offline
Your BIOS clock was set correctly to the current local time, or to UTC? If you have UTC set in rc.conf, your BIOS clock and system clock will be 5 hours apart in the eastern time zone.
Offline
Pages: 1