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.
Mike Snitzer msnitzer at plogic.comMon Jun 24 11:13:56 PDT 2002
- Previous message: Clock Synchronization
- Next message: Clock Synchronization
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert G. Brown (rgb at phy.duke.edu) said: > On a typical client we use: > > # > server ntpsvr1.phy.duke.edu > server ntpsvr2.phy.duke.edu > server ntpsvr3.phy.duke.edu > # > driftfile /etc/ntp/drift > multicastclient # listen on default 224.0.1.1 > broadcastdelay 0.008 > # > authenticate no > > where the servers are even simpler: > > # > server clock.radonc.duke.edu > driftfile /etc/ntp/drift in the client you specify multicastclient, but in the server config you do NOT specifiy: broadcast 224.0.1.1 So are you sure that the server is spitting out a multicast on 224.0.1.1? Thanks for your response, but I'm still looking for some broadcast client/server specific insight. What kind of ntpq -p output do you have on the server and clients? Broadcast and multicast with ntp are very similar in configuration.. but the fact that you don't even specify "broadcast" line in the server config is a bit strange. Mike
- Previous message: Clock Synchronization
- Next message: Clock Synchronization
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
