Mailinglist Archive: opensuse (4570 mails)
| < Previous | Next > |
Re: [SLE] Changing time make X go crazy
- From: Synthetic Cartoonz <synthetoonz@xxxxxxxxxxxxx>
- Date: Sun, 6 Nov 2005 02:00:28 +0000 (UTC)
- Message-id: <200511052100.13704.synthetoonz@xxxxxxxxxxxxx>
On Saturday 05 November 2005 20:28, Steven T. Hatton wrote:
> On Saturday 05 November 2005 06:19 pm, Ulf Rasch wrote:
>>[...]
>>Anyway, it is best to use xntp to take care
> > of changing system time. It makes the adjustments in small steps that
> > otherwise could upset some programs. That works of course only if you
> > are connected to the internet.
> Actually, the way I discovered this involves xntp. I normally use xntp,
> but when I decided to strip my system to the bare minimum and rebuild the
> SuSE 10 installation, I neglected to reinstall xntp. I noticed it was
> getting dark fairly early, and reasoned that I had not be telaproted north
> of the artcic circle, nor had the Earth undergone a pole shift. It
> therefore followed that my clock must be wrong. When I installed xntp,
> that's when I noticed the behavior. I have an internal server set up so
> that I /can/ get updates without hitting the internet. That insures that
> my systems are internally synchronized, but I still need a connection to
> get the ntp server synched up with the rest of the world.
My home ntpd server refused to accept the time update from the
*.us.pool.ntp.org server pool, reporting this nastygram in the ntp log:
"time correction of -3599 seconds exceeds sanity limit (1000); set clock
manually to the correct UTC time." The system's reported time was about an
hour off due to the clock change last week and the fact that the server was
down on that day (lack of electricity due to a recent hurricane), so the
automatic change never occurred on the server.
After manually poking the generally correct time into the computer and
restarting the ntpd server, then it sync'd and adjusted its time correctly.
> On Saturday 05 November 2005 06:19 pm, Ulf Rasch wrote:
>>[...]
>>Anyway, it is best to use xntp to take care
> > of changing system time. It makes the adjustments in small steps that
> > otherwise could upset some programs. That works of course only if you
> > are connected to the internet.
> Actually, the way I discovered this involves xntp. I normally use xntp,
> but when I decided to strip my system to the bare minimum and rebuild the
> SuSE 10 installation, I neglected to reinstall xntp. I noticed it was
> getting dark fairly early, and reasoned that I had not be telaproted north
> of the artcic circle, nor had the Earth undergone a pole shift. It
> therefore followed that my clock must be wrong. When I installed xntp,
> that's when I noticed the behavior. I have an internal server set up so
> that I /can/ get updates without hitting the internet. That insures that
> my systems are internally synchronized, but I still need a connection to
> get the ntp server synched up with the rest of the world.
My home ntpd server refused to accept the time update from the
*.us.pool.ntp.org server pool, reporting this nastygram in the ntp log:
"time correction of -3599 seconds exceeds sanity limit (1000); set clock
manually to the correct UTC time." The system's reported time was about an
hour off due to the clock change last week and the fact that the server was
down on that day (lack of electricity due to a recent hurricane), so the
automatic change never occurred on the server.
After manually poking the generally correct time into the computer and
restarting the ntpd server, then it sync'd and adjusted its time correctly.
| < Previous | Next > |