[OpenAFS] Problems in stopping the afs-client

[Andrei Maslennikov]

On Sat, 19 Oct 2002, Dr A V Le Blanc wrote:

> Actually, there's a problem running ntp when you run afsd without
> -nosettime: if afsd ever _does_ change the time, it messes up the
> ntp algorithm.  I have AFS servers running ntpd, and rarely more
> than .003 second off from each other; all clients run ntpd as well.
> Occasionally someone starts afsd without -nosettime, and problems
> do occur.
> 
> The present defaults _sound_ reasonable, but evidently cause problems
> in some cases.  The question is, should they be changed?  I think
> the answer is not so obvious.
> 
  
  I see that afsd *IS* adjusting the time to that of the servers.
  So at least clients are in sync and local authentication works.
  Now, whether the servers are set to point to an official time 
  source or not (BTW, in our particular case they do), is in the
  end the decision of a local admin, right it is or wrong.  

  If the time-control part of afsd would not work (or would be
  imprecise or/and hard to maintain), I would be the first to
  vote for defaults' change. As so far nobody has ever complained
  about this, I believe we should better leave them defaults 
  in peace for the time being.

  Andrei.

  PS I do agree that it hardly makes any sense to run both
     ntpd and afsd with settime on the same machine.