[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [suse-security] re: new time



The Wednesday 2004-09-29 at 17:21 -0700, Ben wrote:

> > > Maybe this is right???

Nope.

Looking at the headers of one of your direct mails, it shows:

Received: from *.*.*ntec.net (unknown [202.0.*.*])
    by smtp.*.net.nz (Postfix) with ESMTP id AB607AE56E    for
 <robin1.listas*>; Wed, 29 Sep 2004 14:30:17 +1200 (NZST)
Date: Wed, 29 Sep 2004 14:29:58 -0700

Time can not be the same 14:29 -0700 at your machne and 14:30 +1200 at 
another. One is wrong. Also, spamassassin says:

|X-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,
|    DATE_IN_FUTURE_06_12 autolearn=no version=2.63

Some of yours show DATE_IN_FUTURE_12_24, even worse. So, your time zone is 
wrong.

> i set it to Auckland and now i caint change the time to the correct time
> i remember in mandrake there was a script to set the time etc and it
> set the hwclock at the same time,
> is there a script for suse that does the same, does anyone know???

Nope.

Even if there was, as your time zone is incorrect, time would not be 
correct.

If you want my long answer, go to
http://susefaq.sourceforge.net/howto/time.html 
In fact, there are many answers in that FAQ.


Short answer: 

 - set correct time zone in yast (including local vs UTC settings).
 - set system time using comand line "date" as root. Forget kde.
 - set CMOS clock with hwclock --systohc
 - delete /etc/adjtime

 - check using "date" as user.

After that, yes, you can use ntpdate, or better "rcxntpd ntptimeset", 
after configuring /etc/ntp.conf. Even better, if you have a permanent 
network connection, use xntpd itself - you can configure it in yast.


But all this is offtopic in this list, so for further help, please refer 
to SLE list.

-- 
Cheers,
       Carlos Robinson


-- 
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here