Bugs item #845179, was opened at 2003-11-19 10:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=845179&group_id=9368
Category: Installation Group: Future Status: Open Resolution: None Priority: 5 Submitted By: Jeff Squyres (jsquyres) Assigned to: Nobody/Anonymous (nobody) Summary: ntpconfig assumes internet connectivity Initial Comment: The install scripts for ntpconfig assume that the OSCAR cluster is connected to the greater internet. For example, it assumes that the following public NTP servers can be reached: ntp-1.cso.uiuc.edu ntp0.cornell.edu ntp.cmr.gov If you are installing OSCAR on a disconnected network (say, for a demo at SC2003) where such machines are not available, it causes lengthy timeouts during multiple phases of the OSCAR installation (where ntp is stopped/started and the presence of the /etc/ntp/step-tickers file makes ntp try to sync with an available time server). The scripts should check for connectivity to these servers (e.g., a DNS resolve and/or a ping) before assuming anything. Failing connectivity, they should not be added to step-tickers file. In a worst case scenario, only 127.0.0.1 should be in step-tickers so that the clients can time sync to the head node so that NFS activity will be kosher. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=845179&group_id=9368 ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
