[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Fwd: Re: openntpd and ntpq]
- To: misc@openbsd.org
- Subject: Re: [Fwd: Re: openntpd and ntpq]
- From: Matthias Kilian <kili@outback.escape.de>
- Date: Fri, 3 Sep 2004 00:21:53 +0200
- Content-Disposition: inline
- Mail-Followup-To: misc@openbsd.org
- References: <41346983.1010300@toughguy.net> <apv8j0lgpg38qoq056203q7l295ogjvl81@4ax.com> <4134C879.4010407@toughguy.net> <20040831194441.GA7581@outback.escape.de> <20040831195630.GD9306@schlund.de>
- User-Agent: Mutt/1.3.28i
On Tue, Aug 31, 2004 at 09:56:31PM +0200, Hannah Schroeter wrote:
> >If client and server are 5 minutes off from each other, so what?
>
> >If the NFS implementation isn't completely broken, editing and building
> >on the same client shouldn't be affected by time glitches between client
> >and server.
>
> How so? Does the client stub cache the times? And if so, what happens
> when the cache entries get evicted/replaced? Or does the client set
> *its* times on the file?
After sleeping, thinking, reading, I come to the conclusion that I
probably wrote complete bullshit. Sorry for that.
May be I memoized some ill-caching client I used several years ago.
> >BTW: I recently got a gmake warning about future modification times on a
> >gentoo linux box synchronized to some time hopping (i.e. bad configured)
> >ntp servers. No NFS involved at all. IMO, that should be impossible.
>
> That should depend on the ntpd's options, i.e. whether it steps the
> time at all, or whether it uses only adjtime.
No special configuration, just two server entries. May be a bug in ntpd
or in adjtime.
For openntp, I didn't yet test what happens if it's servers are hopping,
but hopping servers are (or should be) a pathologic case anyway.
Ciao,
Kili