Ivan R. Judson
judson at mcs.anl.gov
Fri Oct 8 09:13:35 CDT 2004
You don't need to be in the same time _zone_ as the server, you need to have
your computers clock kept synchronized.
NTP provides a way to synchronize your clock whatever timezone you are in.
This is important because if your clock is significantly off, your globus
proxy (which is used to get at AG2 resources) won't be valid on the server
(since it's clock is correct).
The popup you are seeing (this addresses randy's question too) indicates
only a warning that you should deal with the situation or expect to have
> -----Original Message-----
> From: owner-ag-tech at mcs.anl.gov
> [mailto:owner-ag-tech at mcs.anl.gov] On Behalf Of Jeremy Mann
> Sent: Friday, October 08, 2004 9:11 AM
> To: ag-tech at mcs.anl.gov
> Subject: [AG-TECH] ntp-1.accessgrid.org
> I got a question regarding the 2.3 VenueClient and NTP. When
> a 2.3 client connects to our venueserver, I get a popup
> message saying the time on the server is 3786 seconds off
> from ntp-1.accessgrid.org. Why is this check being done? Our
> server isn't in the same timezone as ANL, so right now we can
> only login to the ANL server.
> Can I edit the python file and change that reference to our
> NTP server? If I do change it, will that mean our client
> can't connect to the ANL venues anymore?
> Jeremy Mann
> jeremy at biochem.uthscsa.edu
> University of Texas Health Science Center Bioinformatics Core
> Facility http://www.bioinformatics.uthscsa.edu
> Phone: (210) 567-2672
More information about the ag-tech