You are not logged in.
in addition please post the output of
hwclock --show --localtime; date
# hwclock --show --localtime; date
Sun Dec 17 22:23:14 2006 -0.809883 seconds
Sun Dec 17 13:25:08 PST 2006
Don't really know what to make of that.
I always roll 20s on my disbelieve checks.
You better believe it.
Offline
which one is right? if its date then do
hwclock --systohc --localtime
then run the command again and see if they're both the same. If its hwclock then run
hwclock --hctosys --localtime
and run it again.
Offline
Yes, I know that. My problem is, if I try to set the time with ntpdate (after setting both hwclock and system time correctly) it gets reset to 10 hours earlier or some nonsense like that, without fail.
I always roll 20s on my disbelieve checks.
You better believe it.
Offline
"Sun Dec 17 13:25:08 PST 2006"
That's not Europe/Berlin, for sure.
1000
Offline
"Sun Dec 17 13:25:08 PST 2006"
That's not Europe/Berlin, for sure.
That's kind of my point.
I always roll 20s on my disbelieve checks.
You better believe it.
Offline
That's Pacific Standard Time.
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein
Offline
I simply cannot duplicate your issue. I changed my timezone to yours and rebooted. Then I ran ntpdate, and as far as I can tell was placed in your timezone just fine. I tried the timezone both with and without quotes since I don't have them in my rc.conf. I rebooted a few times, too.
[root@pinkwater ~]# ntpdate pool.ntp.org
18 Dec 02:09:28 ntpdate[3933]: adjust time server 65.119.47.241 offset -0.000832 sec
[root@pinkwater ~]# date
Mon Dec 18 02:09:33 CET 2006
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein
Offline
Well, maybe it's the rebooting. I've already asked what I have to do to make my system reevaluate rc.conf, because I run linux so I don't have to reboot. I take pains so I don't have to, and up to now, I've always found ways to solve my problems without having to do that (you know, sort of kernel recompiles and similar).
Is it possible that this is simply because my system hasn't yet gotten the fact that my rc.conf says my timezone is Europe/Berlin? I remember just putting "Berlin" at install, then realizing that was wrong and changing it to Europe/Berlin. I don't think I rebooted afterwards. If the answer is this simple, I hope you know of a way of fixing it without rebooting.
I always roll 20s on my disbelieve checks.
You better believe it.
Offline
Genius. Have a look at /etc/inittab and the rc. files in /etc to see how and when things get evaluated.
Running Arch certainly won't lead to high uptimes, at least not without ignoring the kernel packages on upgrades.
1000
Offline
Erm...
What's the point of running ntpdate if you haven't rebooted and you have hand-set your time? I'm honestly curious.
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein
Offline
What's the point of running ntpdate if you haven't rebooted and you have hand-set your time? I'm honestly curious.
The point of running ntpdate is getting the correct time. I simply wasn't aware that rc.conf only gets evaluated at boot, which is why I expected to get the correct result after correcting it. Eh, well.
I feel like I'm on Windows. "OMG, you have changed a configuration file! You better reboot!". Fiddlesticks. Maybe I'll manage to squeeze in a reboot on the weekend.
I always roll 20s on my disbelieve checks.
You better believe it.
Offline
> The point of running ntpdate is getting the correct time.
Right, and you got the correct time, including the correct timezone offset.
Again, look at /etc/rc.sysinit. Furthermore, _all_ operating systems evaluate stuff like that only on boot. There's no magical background process just waiting for changes on crucial system files to reread and apply them.
1000
Offline
Yes, but with most stuff on linux I at least found a way of manually telling the system to reevaluate it. Anyway, I'm guessing my problem is "solved".
I always roll 20s on my disbelieve checks.
You better believe it.
Offline
source /etc/rc.conf
ln -sf /usr/share/zoneinfo/$TIMEZONE /etc/localtime
OMG!!!!
I just read rc.sysinit for you and gave you a solution!!!
OMG!!!
Offline
OMG! Way awesome!
I always roll 20s on my disbelieve checks.
You better believe it.
Offline
source /etc/rc.conf ln -sf /usr/share/zoneinfo/$TIMEZONE /etc/localtime
OMG!!!!
I just read rc.sysinit for you and gave you a solution!!!OMG!!!
Thanks for that. I may sound like a dumbass for saying this, but I never would have thought to look in there. I'll keep it in mind for the future.
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein
Offline
source /etc/rc.conf ln -sf /usr/share/zoneinfo/$TIMEZONE /etc/localtime
OMG!!!!
I just read rc.sysinit for you and gave you a solution!!!
Starting from initscripts-0.8-2 /etc/localtime is a copy, not symlink, now.
Also, all known timezone problems are fixed. Please try it.
to live is to die
Offline