Mailinglist Archive: opensuse-kde (310 mails)
| < Previous | Next > |
OT: Includes a free BOFH story [was: [suse-kde] Re: [SLE] Speaking of time?]
- From: Christopher Mahmood <ckm@xxxxxxxx>
- Date: Fri, 10 May 2002 17:39:30 -0700
- Message-id: <20020511003930.GF25120@xxxxxxxxxxxxxxxxxx>
* Leendert Meyer (leen.meyer@xxxxxxx) [020510 16:09]:
> Ah, my fault to assume you knew KDE ;-).
A safe assumption, this is suse-kde afterall.
> The clock applet in kicker is AFAIK passive, i.e. it only shows time, and
> doesn't change it. However the time can be changed _by_the_user_ in KDE's
> Control Center.
Hmmm...sounds complicated.
> Hmm, hostnames instead of ip#, why is that? I don't see the benefit of that.
> The hostnames could (at some point in time) get different ip#, but those are
> fixed in /etc/hosts. I would have to change that file.
The idea is that you don't want to risk a DNS timeout at boot and
not get the time set correctly before other services started. For
example, I was once working on a customers mailserver and he had the
xntp init script running last, after sendmail, named, etc. The
hwclock turned out to several days ahead of reality. So the system
starts to boot, sendmail starts and notices that it has all of this
old undelievered mail sitting in the queue and decides that it's
time to bounce all of it as undelieverable. Afterall, it was
sitting in the queue for 4 days.
But yes, the PTR records might change at some point. That's why I
specified public timeservers. If you are in charge you'll know that
you'll break a lot of stuff if you do change them.
--
-ckm
> Ah, my fault to assume you knew KDE ;-).
A safe assumption, this is suse-kde afterall.
> The clock applet in kicker is AFAIK passive, i.e. it only shows time, and
> doesn't change it. However the time can be changed _by_the_user_ in KDE's
> Control Center.
Hmmm...sounds complicated.
> Hmm, hostnames instead of ip#, why is that? I don't see the benefit of that.
> The hostnames could (at some point in time) get different ip#, but those are
> fixed in /etc/hosts. I would have to change that file.
The idea is that you don't want to risk a DNS timeout at boot and
not get the time set correctly before other services started. For
example, I was once working on a customers mailserver and he had the
xntp init script running last, after sendmail, named, etc. The
hwclock turned out to several days ahead of reality. So the system
starts to boot, sendmail starts and notices that it has all of this
old undelievered mail sitting in the queue and decides that it's
time to bounce all of it as undelieverable. Afterall, it was
sitting in the queue for 4 days.
But yes, the PTR records might change at some point. That's why I
specified public timeservers. If you are in charge you'll know that
you'll break a lot of stuff if you do change them.
--
-ckm
| < Previous | Next > |