-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Should do - run 'ntqp -p' to see the current peers a workstation is looking at. Also check the system logs - they'll note any issues.
Cheers, James Harrison On 18/11/2011 23:30, Nathan Steele wrote: > Ok, I have this setup on my server, what do I need to do on the > workstations? I installed NTP and pointed it to my server IP, will that > do the trick? > > Nathaniel C. Steele > Assistant Chief Engineer/Technical Director > WTRM-FM / TheCrossFM > > > On 11/18/2011 12:34 PM, James Harrison wrote: > This is actually pretty simple to do. > > Just install ntp (as per your distro - if it's ubuntu, apt-get install > ntp, I'm sure suse/centos are similar), then configure it (/etc/ntp.conf): > > Configure with some geographically local servers - I use two servers > hosted by NPL (the National Physical Laboratory) in the UK along with > four servers from the UK NTP pool.: > > server ntp1.npl.co.uk iburst > server ntp2.npl.co.uk iburst > server 0.uk.pool.ntp.org iburst > server 1.uk.pool.ntp.org iburst > server 2.uk.pool.ntp.org iburst > server 3.uk.pool.ntp.org iburst > > If you can get access to any stratum-1 servers (we also use the JANET > NTP server, which is stratum-1), do so. > > We also want to fall back on the local clock source should we have no > remote clocks: > > server 127.127.1.0 > fudge 127.127.1.0 stratum 12 > > Drift configuration should be done for you but if not, add something like: > > driftfile /var/lib/ntp/ntp.drift > > > Next you need to setup the security so your subnet can access it and > localhost can check to ensure all is well: > > restrict default kod nomodify notrap nopeer noquery > restrict 127.0.0.1 > > And now we insert our subnets: > > restrict 127.219.53.0 mask 255.255.252.0 nomodify nopeer notrap > restrict 127.219.88.0 mask 255.255.252.0 nomodify nopeer notrap > # (and if we have a single machine we need to have access:) > restrict 127.79.141.232 mask 255.255.255.255 nomodify nopeer notrap > > And some handy statistics: > > statsdir /var/ntp/ntpstats/ > statistics loopstats peerstats clockstats > filegen loopstats file loopstats type day enable > filegen peerstats file peerstats type day enable > filegen clockstats file clockstats type day enable > > > As for the GPS clock- that appears to be a PVT6 version Oncore receiver. > http://www.eecis.udel.edu/~mills/ntp/html/drivers/driver30.html > > A driver for ntpd is available so you just need to plug it into a serial > port and plug in a GPS antenna on the antenna port, then configure ntpd, > which will be something like this: > http://twiki.ntp.org/bin/view/Support/ConfiguringMotorolaOncoreRefclocks > > You should absolutely get the GPS clock configured ("the generated PPS > pulse is referenced to UTC(GPS) with better than 50 nsec (1 sigma) > accuracy") - it'll perform better than ntp alone, and your server will > then be stratum 1. > > Don't forget also to set up a timelord@ address for your domain - this > helps people contact you in the event of an issue with your ntp server. > > Hope that helps! > > Cheers, > James Harrison > > > On 18/11/2011 17:18, Nathan Steele wrote: > >>> You might be on to something, the liners are all hard timed, but they > >>> are set to "make next" if the previous song is still playing at the time > >>> so as to not cut it off. I will go set the next one tostart immediately > >>> and see if that fixes it. > >>> > >>> > >>> Getting NTP setup has been on my todo list. We have a GPS device that > >>> was used with our very old and custom coded automation system, but I can > >>> not seem to find any info on it. It is just a little black box that > >>> reads on the label: > >>> Motorola > >>> Model No: PVT602N323 > >>> > >>> googling that gave me very little and nothing useful that I found. It's > >>> only connections are an antenna BNC and a DB-9 that is the power in and > >>> seriel data link, I have the special cable for it around here > somewhere..... > >>> Anyway, what I want to do is setup the server to use either this GPS or > >>> a remote NTP server, and have all of my workstations getting NTP from > >>> the server. I've read up on it a little but am still not real sure how > >>> to do it. > >>> > >>> Nathaniel C. Steele > >>> Assistant Chief Engineer/Technical Director > >>> WTRM-FM / TheCrossFM > >>> > >>> > >>> On 11/18/2011 12:02 PM, Dan Mills wrote: > >>>> On Fri, 2011-11-18 at 11:25 -0500, Nathan Steele wrote: > >>>>> I looked in RD adminand the only thing that > >>>>> even remotely looked like it could affect the clock was a setting called > >>>>> "Check Time SYNC". what does this do? > >>>> Check time sync just makes the clock in the top left corner of rdairplay > >>>> flash red if the PCs clock is not locked to an external reference by > >>>> something like NTP. > >>>> It is mainly useful for machines involved in things like satellite links > >>>> where a few seconds can cause a train wreck and NTP or GPS > >>>> synchronisation is in use. > >>>> NTP is a good idea generally, and is worth setting up if it is not > >>>> already. > >>>> > >>>> What time does the PC 'date' command give, and is it correct (Also is > >>>> the timezone correct)? > >>>> > >>>> Final thought, has there been anything hard timed since the clocks > >>>> changed? Rdairplay will quite happily keep running events with no fixed > >>>> start time based upon the start time of the log unless there is > >>>> something to force a specific start time, and IIRC that logic does not > >>>> understand DST. > >>>> You need to over schedule to allow for the extra hour or the thing will > >>>> quite happily either stop or just keep going depending on the transition > >>>> type. > >>>> > >>>> > >>>> Regards, Dan. > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Rivendell-dev mailing list > >>>> [email protected] > >>>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > >>>> > >>>> > >>>> > >>> _______________________________________________ > >>> Rivendell-dev mailing list > >>> [email protected] > >>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >> >> >> > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7G9f0ACgkQmJV2s0zjsDj4jQCfaFNG9OJalQef7FbilG1mO9Kr YyQAmwROb1DthqHiEHn02QuZVXZjeYwQ =tGsu -----END PGP SIGNATURE----- _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
