Clock Synchronization
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Jim Meyer purp at wildbrain.comWed May 8 09:58:22 PDT 2002
- Previous message: Clock Synchronization
- Next message: Good Tutorial for Clusters
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 2002-05-08 at 09:25, Josip Loncaric wrote: > "Robert G. Brown" wrote: > > > > I personally think that networked systems, nodes or not, should have the > > time network synchronized if at all possible. > > > > We use ntpd to keep everything sync'd. > > I concur -- ntpd is very good, and it can be very easy on your internal > network (within your cluster, just use broadcast client/server model > instead of polling). > > Unsynchronized systems can misbehave, particularly with schedulers etc. Not to mention that troubleshooting a cross-system problem takes on nightmarish proportions if you're unable to compare system logs with any reasonable time correspondence. --j, an ntpd fan as well. -- Jim Meyer, Geek At Large purp at wildbrain.com
- Previous message: Clock Synchronization
- Next message: Good Tutorial for Clusters
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
