[OpenAFS] bad sinchronization clock from a fileserver

Neulinger, Nathan nneul@umr.edu
Wed, 16 Feb 2005 13:58:42 -0600


It's disabled by default, you have to explicitly choose to compile it
in. I certainly hope the standard binary builds are not set that way.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-6679
UMR Information Technology             Fax: (573) 341-4216
=20

> -----Original Message-----
> From: openafs-info-admin@openafs.org=20
> [mailto:openafs-info-admin@openafs.org] On Behalf Of Derek Atkins
> Sent: Wednesday, February 16, 2005 1:53 PM
> To: Jeffrey Hutzelman
> Cc: openafs-info@openafs.org
> Subject: Re: [OpenAFS] bad sinchronization clock from a fileserver
>=20
> Jeffrey Hutzelman <jhutz@cmu.edu> writes:
>=20
> > Also, you should be using real NTP from http://www.ntp.org/=20
> and not the=20
> > ancient stuff that's included in the openafs distribution.
>=20
> Haven't we removed that old cruft from OpenAFS, yet?
>=20
> -derek
> --=20
>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>        Member, MIT Student Information Processing Board  (SIPB)
>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>        warlord@MIT.EDU                        PGP key available
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20
>=20