From: Bruno Lustosa <bruno.lists@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ntp problem
Date: Tue, 23 Aug 2005 11:26:11 -0300 [thread overview]
Message-ID: <b9e0c3fe0508230726389ee819@mail.gmail.com> (raw)
In-Reply-To: <2ab8d39a050823071990b8aad@mail.gmail.com>
On 8/23/05, krzaq <krzakers@gmail.com> wrote:
> Hmmmm...
> If you specify one timeserver, ntp cannot tell which clock is drifting
> away (local
> or remote). Ntpd trusts the local clock more than the remote one.
> Large offsets cause ntpd to discard 192.168.7.1 as reliable timesource.
> Try adding on this one machine more time servers and observe what will happen.
I have another network of servers that are on a hosting company. I'll
set up ntpd on one of those machines and let the internal machines get
in sync with these 2 servers and see what happens.
I guess I have lots of things to learn about ntp's internals.
Thanks
--
Bruno Lustosa, aka Lofofora | Email: bruno@lustosa.net
Network Administrator/Web Programmer | ICQ: 1406477
Rio de Janeiro - Brazil |
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-23 14:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 12:36 [gentoo-user] ntp problem Bruno Lustosa
2005-08-23 13:14 ` krzaq
2005-08-23 13:21 ` Bruno Lustosa
2005-08-23 13:25 ` Uwe Thiem
2005-08-23 14:30 ` Bruno Lustosa
2005-08-23 15:46 ` Michael Kintzios
2005-08-23 17:50 ` Bruno Lustosa
2005-08-23 13:26 ` kashani
2005-08-23 13:29 ` Bruno Lustosa
2005-08-23 14:19 ` krzaq
2005-08-23 14:26 ` Bruno Lustosa [this message]
2005-08-23 14:28 ` Bruno Lustosa
2005-08-24 1:25 ` W.Kenworthy
-- strict thread matches above, loose matches on Subject: below --
2006-02-22 7:32 [gentoo-user] NTP problem Anthony E. Caudel
2006-02-22 8:10 ` Brandon Enright
2006-02-22 8:41 ` Anthony E. Caudel
2006-02-22 16:29 ` Brandon Enright
2006-02-22 18:38 ` Anthony E. Caudel
2006-02-22 19:05 ` Boyd Stephen Smith Jr.
2006-02-22 19:13 ` Brandon Enright
2006-02-22 20:03 ` Boyd Stephen Smith Jr.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9e0c3fe0508230726389ee819@mail.gmail.com \
--to=bruno.lists@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox