Index: [Article Count Order] [Thread]

Date:  Fri, 01 Sep 2006 13:08:41 +0200
From:  Dennis <dennis (at mark) mixfans.org>
Subject:  [coba-e:06668] Re: Time problem after update?
To:  coba-e (at mark) bluequartz.org
Message-Id:  <44F814B9.9000009 (at mark) mixfans.org>
In-Reply-To:  <44F8126C.2010903 (at mark) mixfans.org>
References:  <001d01c6cd32$81f7fe10$1e00a8c0 (at mark) TOWER> <20060831214128.GA90350 (at mark) xs4all.nl> <44F8126C.2010903 (at mark) mixfans.org>
X-Mail-Count: 06668

I am now checking if switching timezones forth / back is the solution 
for me.

Dennis wrote:
> I did the same but see this
>
> Sep  1 06:57:41 wb sendmail[14854]: ruleset=check_relay, 
> arg1=[83.102.141.18], arg2=127.0.0.2, relay=[83.102.141.18], 
> reject=550 5.7.1 - Email blocked by SpamCop see: 
> http://spamcop.net/bl.shtml?83.102.141.18
> Sep  1 06:57:41 wb sendmail[14855]: ruleset=check_relay, 
> arg1=[83.102.141.18], arg2=127.0.0.2, relay=[83.102.141.18], 
> reject=550 5.7.1 - Email blocked by SpamCop see: 
> http://spamcop.net/bl.shtml?83.102.141.18
> Sep  1 12:57:41 wb in.qpopper[14850]: (v4.0.5) POP login by user 
> "xxxx" at (sys.dennis) 192.168.1.99
> Sep  1 12:57:41 wb in.qpopper[14849]: (v4.0.5) POP login by user 
> "xxxx" at (sys.dennis) 192.168.1.99
> Sep  1 12:57:41 wb in.qpopper[14850]: Stats: around 0 0 0 0 sys.dennis 
> 192.168.0.99
> Sep  1 12:57:41 wb in.qpopper[14849]: Stats: dennis 0 0 0 0 sys.dennis 
> 192.168.0.99
>
> So you think it's okay but it's switching backwards / forwards ..
> I even removed the NTP server I used.. no solution ..
>
>
>
> Maurice de Laat wrote:
>> On Thu, Aug 31, 2006 at 08:20:23PM +0100, Richard Monks wrote:
>>
>>  
>>> I'm in the process of writing some PHP and noticed that the time on my
>>> server has been set back 5 hours - reading 15:XX instead of 20:XX.  
>>> Looking
>>> at System Settings->Time, the hours list is messed up, with '12' as the
>>> first option and 1-11 following.
>>>  
>>> I have pool.ntp.org set as my time server and that doesn't appear to be
>>> having any effect either.  Date seems to be OK.
>>>  
>>> This has happened on both of the servers I've updated - is it a 
>>> result of
>>> the update?
>>>     
>>
>> Looks the same here.
>> It seems to me that the timezone was incorrect:
>> [admin@arie ~]$ date
>> Thu Aug 31 17:36:44 EDT 2006
>>
>> I went into the GUI. Didn't change the timesetting, but saved them 
>> again. It now looks correct:
>> [admin@arie ~]$ date
>> Thu Aug 31 23:38:17 CEST 2006
>>   
>
>