On Friday 26 October 2018 09:53:39 Greg Wooledge wrote:
> On Fri, Oct 26, 2018 at 09:29:38AM -0400, Gene Heskett wrote:
> > and it goes out on the net and checks
> > all servers before ntpq -p is completed, take 5 or 6 seconds to do
> > that,
>
> That's DNS resolution. It's looking up the IP addr
On Fri, Oct 26, 2018 at 09:44:47AM -0400, Gene Heskett wrote:
As I'm fond of saying TANSTAAFL. If we all, with multiple machine sites,
did this it would make a measureable difference in bandwidth used
If people want to set up local ntp servers, great. But just configure
the clients with a ser
On Fri, Oct 26, 2018 at 09:29:38AM -0400, Gene Heskett wrote:
> and it goes out on the net and checks
> all servers before ntpq -p is completed, take 5 or 6 seconds to do that,
That's DNS resolution. It's looking up the IP addresses so it can
report names to you. If you want to skip that, you
On Friday 26 October 2018 09:01:50 Curt wrote:
> On 2018-10-25, Gene Heskett wrote:
> > Now this machine shows for ntpq -p:
> > remote refid st t when poll reach delay
> > offset jitter
> >
> >==
On Friday 26 October 2018 08:26:47 Greg Wooledge wrote:
> On Thu, Oct 25, 2018 at 05:36:21PM -0400, Gene Heskett wrote:
> > I put the router back on pool.ntp.org, but had to reboot it to take
> > effect.
> >
> > Now this machine shows for ntpq -p:
> > remote refid st t when pol
On 2018-10-25, Gene Heskett wrote:
> Now this machine shows for ntpq -p:
> remote refid st t when poll reach delay offset jitter
>==
> +159.203.158.197 45.33.103.94 3 u 59 643 19.551
On Thu, Oct 25, 2018 at 05:36:21PM -0400, Gene Heskett wrote:
> I put the router back on pool.ntp.org, but had to reboot it to take effect.
>
> Now this machine shows for ntpq -p:
> remote refid st t when poll reach delay offset jitter
> ===
On Thursday 25 October 2018 16:50:11 Greg Wooledge wrote:
> On Thu, Oct 25, 2018 at 04:40:46PM -0400, Gene Heskett wrote:
> > I added the router to the server list for this machine and get this
> > for an ntpq -p: remote refid st t when poll reach
> > delay offset jitter
> > ==
On Thu, Oct 25, 2018 at 04:40:46PM -0400, Gene Heskett wrote:
> I added the router to the server list for this machine and get this for an
> ntpq -p:
> remote refid st t when poll reach delay offset jitter
> ==
On Thursday 25 October 2018 14:08:47 Curt wrote:
> On 2018-10-25, Gene Heskett wrote:
> > On Thursday 25 October 2018 09:32:08 Curt wrote:
> >> On 2018-10-25, Greg Wooledge wrote:
> >> >> 2 machines report:
> >> >> pi@picnc:/etc $ ntpq -p
> >> >> No association ID's returned
> >> >
> >> > I've l
On 2018-10-25, Gene Heskett wrote:
> On Thursday 25 October 2018 09:32:08 Curt wrote:
>
>> On 2018-10-25, Greg Wooledge wrote:
>> >> 2 machines report:
>> >> pi@picnc:/etc $ ntpq -p
>> >> No association ID's returned
>> >
>> > I've literally never seen such a message before. I googled it, and
>>
On Thursday 25 October 2018 09:32:08 Curt wrote:
> On 2018-10-25, Greg Wooledge wrote:
> >> 2 machines report:
> >> pi@picnc:/etc $ ntpq -p
> >> No association ID's returned
> >
> > I've literally never seen such a message before. I googled it, and
> > there are definitely results that look rele
On 2018-10-25, Greg Wooledge wrote:
>> 2 machines report:
>> pi@picnc:/etc $ ntpq -p
>> No association ID's returned
>
> I've literally never seen such a message before. I googled it, and there
> are definitely results that look relevant. After adding "broadcast" to
> the search terms, I came u
On Wed, Oct 24, 2018 at 06:23:49PM -0400, Gene Heskett wrote:
> The idea is to reduce the loading of 7 machines all banging one the level
> 1 and 2 servers by designating one machine to bang of the debian pool,
> and then broadcast it on the local 192.169.xx.xx net so all the others
> stay withi
On Wednesday, October 24, 2018 07:10:00 PM rhkra...@gmail.com wrote:
> On Wednesday, October 24, 2018 06:25:46 PM Gene Heskett wrote:
> > On Wednesday 24 October 2018 11:07:05 rhkra...@gmail.com wrote:
> > > I think that covers what I was going to say, but in an attempt to show
> > > off my knowled
On Wednesday, October 24, 2018 06:25:46 PM Gene Heskett wrote:
> On Wednesday 24 October 2018 11:07:05 rhkra...@gmail.com wrote:
> > I think that covers what I was going to say, but in an attempt to show
> > off my knowledge (or lack thereof) ;-)
> >
> > As I understand it, NTP tries to get an app
On Wednesday 24 October 2018 11:07:05 rhkra...@gmail.com wrote:
> On Wednesday, October 24, 2018 10:27:04 AM john doe wrote:
> > On 10/24/2018 2:44 PM, Greg Wooledge wrote:
> > > On Wed, Oct 24, 2018 at 08:22:49AM -0400, Gene Heskett wrote:
> > >> I has this machine running ntp normally, and set t
On Wednesday 24 October 2018 10:27:04 john doe wrote:
> On 10/24/2018 2:44 PM, Greg Wooledge wrote:
> > On Wed, Oct 24, 2018 at 08:22:49AM -0400, Gene Heskett wrote:
> >> I has this machine running ntp normally, and set to broadcast on
> >> the $local/24 network.
> >
> > I've never used NTP in "br
On Wednesday, October 24, 2018 10:27:04 AM john doe wrote:
> On 10/24/2018 2:44 PM, Greg Wooledge wrote:
> > On Wed, Oct 24, 2018 at 08:22:49AM -0400, Gene Heskett wrote:
> >> I has this machine running ntp normally, and set to broadcast on the
> >> $local/24 network.
> >
> > I've never used NTP i
On 10/24/2018 2:44 PM, Greg Wooledge wrote:
> On Wed, Oct 24, 2018 at 08:22:49AM -0400, Gene Heskett wrote:
>> I has this machine running ntp normally, and set to broadcast on the
>> $local/24 network.
>
> I've never used NTP in "broadcast" mode.
>
> If it were me, I would simply use the normal
On Wed, Oct 24, 2018 at 08:22:49AM -0400, Gene Heskett wrote:
> I has this machine running ntp normally, and set to broadcast on the
> $local/24 network.
I've never used NTP in "broadcast" mode.
If it were me, I would simply use the normal configuration in which
each client system has the NTP se
I has this machine running ntp normally, and set to broadcast on the
$local/24 network.
I have 6 other machines on this local network, but only 2 are staying
with this machine timewise.
Does anyone have a clue why the other 4 are not, atm up to 35 seconds
diff between them? They all have th
22 matches
Mail list logo
