Ask Bj?rn Hansen writes: >> On Feb 23, 2015, at 4:37 PM, Harlan Stenn <[email protected]> wrote: >> >> You might not need orphan mode at all - just the plain local refclock >> driver. >> >> You might also just need a "customized" leapseconds file. > > Yeah, that was my first test =E2=80=94 just: > > server 127.127.1.1 minpoll 4 maxpoll 5 > fudge 127.127.1.1 stratum 4 > leapfile "/etc/ntp/leap-seconds.list" > > The documentation[1] says that =E2=80=9Corphan mode=E2=80=9D is the = > replacement for the local clock, so that=E2=80=99s why I tried that too. = > (It also says that since 4.2.5p101 ntpd can run in =E2=80=9Cpure orphan = > mode=E2=80=9D, so that=E2=80=99s why I tried it that way, too). > > [1] http://support.ntp.org/bin/view/Support/OrphanMode
OK, first, in general, most folks want Orphan Mode. There are *very few* cases where one wants a local refclock. This may or may not be one of them. I am *pretty sure* that it doesn't matter which one you use. The key element is probably that you have a leapfile on your box that says when you want the leap to happen, and you set the time on this box with no external servers. In this case, with either orphan mode or with a local refclock, the local machine should offer "sync'd" time at whatever stratum is selected. Please pick something so if somebody stumbles across this machine it won't be "believed". H _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
