Re: NTP wasn't working

Godzilla

After several days of my system clock showing the incorrect time until I
entered YAST and did a manual test of the NTP daemon, I tried putting in a
new CMOS battery. My settings were to access NTP at boot. The battery that
I removed DID test bad. This morning, when I turned the machine on, I was
anxious to see if the problem had been resolved.

It booted up normally, but when the opening SUSE window appeared it showed a
time hours slow for a few seconds. Then, without any intervention on my
part the screen went dark for a few moments until it asked for my login
again. After doing this, the opening SUSE window appeared again, this time
showing the correct time. A look at /var/log/ntp confirmed that it was
synced after the second pass. My time is again correct, but why is the
screen saver kicking on and making me log in twice?

Godzilla

C. (http://symcbean.blogspot.com/)

On Jan 8, 12:47 pm, Godzilla <godzi...@monsters.org> wrote:
>
> It booted up normally, but when the opening SUSE window appeared it showed a
> time hours slow for a few seconds. Then, without any intervention on my
> part the screen went dark for a few moments until it asked for my login
> again. After doing this, the opening SUSE window appeared again, this time
> showing the correct time. A look at /var/log/ntp confirmed that it was
> synced after the second pass. My time is again correct, but why is the
> screen saver kicking on and making me log in twice?
>

So you're saying your screensaver started in the background at say
10:00, and you didn't do anything, then the screensaver saw the time
was 10:15, and you want to know why it kicked in? Have you had your
coffee / medication yet today?

C.

C. (http://symcbean.blogspot.com/)

On Jan 8, 12:47 pm, Godzilla <godzi...@monsters.org> wrote:
>
> It booted up normally, but when the opening SUSE window appeared it showed a
> time hours slow for a few seconds. Then, without any intervention on my
> part the screen went dark for a few moments until it asked for my login
> again. After doing this, the opening SUSE window appeared again, this time
> showing the correct time. A look at /var/log/ntp confirmed that it was
> synced after the second pass. My time is again correct, but why is the
> screen saver kicking on and making me log in twice?
>

So you're saying your screensaver started in the background at say
10:00, and you didn't do anything, then the screensaver saw the time
was 10:15, and you want to know why it kicked in? Have you had your
coffee / medication yet today?

C.

C. (http://symcbean.blogspot.com/)

On Jan 8, 12:47 pm, Godzilla <godzi...@monsters.org> wrote:
>
> It booted up normally, but when the opening SUSE window appeared it showed a
> time hours slow for a few seconds. Then, without any intervention on my
> part the screen went dark for a few moments until it asked for my login
> again. After doing this, the opening SUSE window appeared again, this time
> showing the correct time. A look at /var/log/ntp confirmed that it was
> synced after the second pass. My time is again correct, but why is the
> screen saver kicking on and making me log in twice?
>

So you're saying your screensaver started in the background at say
10:00, and you didn't do anything, then the screensaver saw the time
was 10:15, and you want to know why it kicked in? Have you had your
coffee / medication yet today?

C.

Godzilla

C. (http://symcbean.blogspot.com/) wrote:

> On Jan 8, 12:47 pm, Godzilla <godzi...@monsters.org> wrote:
>>
>> It booted up normally, but when the opening SUSE window appeared it
>> showed a time hours slow for a few seconds. Then, without any
>> intervention on my part the screen went dark for a few moments until it
>> asked for my login again. After doing this, the opening SUSE window
>> appeared again, this time showing the correct time. A look at
>> /var/log/ntp confirmed that it was synced after the second pass. My time
>> is again correct, but why is the screen saver kicking on and making me
>> log in twice?
>>
>
> So you're saying your screensaver started in the background at say
> 10:00, and you didn't do anything, then the screensaver saw the time
> was 10:15, and you want to know why it kicked in? Have you had your
> coffee / medication yet today?
>
> C.

For the benefit of those who are not conversant with the English language,
the screen saver kicked in INSTANTLY, not after 15 minutes.

>> showed a time hours slow for a few seconds.

Godzilla

Godzilla

C. (http://symcbean.blogspot.com/) wrote:

> On Jan 8, 12:47 pm, Godzilla <godzi...@monsters.org> wrote:
>>
>> It booted up normally, but when the opening SUSE window appeared it
>> showed a time hours slow for a few seconds. Then, without any
>> intervention on my part the screen went dark for a few moments until it
>> asked for my login again. After doing this, the opening SUSE window
>> appeared again, this time showing the correct time. A look at
>> /var/log/ntp confirmed that it was synced after the second pass. My time
>> is again correct, but why is the screen saver kicking on and making me
>> log in twice?
>>
>
> So you're saying your screensaver started in the background at say
> 10:00, and you didn't do anything, then the screensaver saw the time
> was 10:15, and you want to know why it kicked in? Have you had your
> coffee / medication yet today?
>
> C.

For the benefit of those who are not conversant with the English language,
the screen saver kicked in INSTANTLY, not after 15 minutes.

>> showed a time hours slow for a few seconds.

Godzilla

Godzilla

C. (http://symcbean.blogspot.com/) wrote:

> On Jan 8, 12:47 pm, Godzilla <godzi...@monsters.org> wrote:
>>
>> It booted up normally, but when the opening SUSE window appeared it
>> showed a time hours slow for a few seconds. Then, without any
>> intervention on my part the screen went dark for a few moments until it
>> asked for my login again. After doing this, the opening SUSE window
>> appeared again, this time showing the correct time. A look at
>> /var/log/ntp confirmed that it was synced after the second pass. My time
>> is again correct, but why is the screen saver kicking on and making me
>> log in twice?
>>
>
> So you're saying your screensaver started in the background at say
> 10:00, and you didn't do anything, then the screensaver saw the time
> was 10:15, and you want to know why it kicked in? Have you had your
> coffee / medication yet today?
>
> C.

For the benefit of those who are not conversant with the English language,
the screen saver kicked in INSTANTLY, not after 15 minutes.

>> showed a time hours slow for a few seconds.

Godzilla