[OpenAFS] bad sinchronization clock from a fileserver
ted creedon
tcreedon@easystreet.com
Wed, 16 Feb 2005 09:57:15 -0800
The reason for -nosettime is that NTP time should be used.
1. RTFM there are lots of good sites to google look at ntp.conf and
/etc/xinted.d/time
2. set nettime up to grab time from 2 external TCP/IP sites (or gps). The
typical ISP has Cisco routers you can point to...
3. set your clients up to grab with your servers
You need to be within (settable) 5 sec to have logins work
tedc
-----Original Message-----
From: openafs-info-admin@openafs.org [mailto:openafs-info-admin@openafs.org]
On Behalf Of Jim Rees
Sent: Wednesday, February 16, 2005 9:06 AM
To: rogbazan
Cc: openafs-info@openafs.org
Subject: Re: [OpenAFS] bad sinchronization clock from a fileserver
This caused that a Unix Client forward its clock.
How can i set up afs client to not synchronize with afs servers?
You want the -nosettime option to afsd. We really need to make this the
default, but I don't have the necessary ambition to update all the
documentation and release notes.
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info