[comp.protocols.time.ntp] Misc. questions about xntpd

mrapple@quack.sac.ca.us (Nick Sayer) (05/28/91)

I have a single Sun 3/160, and a CHU clock with a lousy
antenna (unfortuately it can't be helped). When propogation is
good, I can get once-a-minute-reachability for all but 8 hours
in the morning. When propogation is bad, that OAMR can be had
for 12 hours. Here's my conf file:

#
# xntp config file
#
# First, set up the security
#
keys /etc/ntp.keys
requestkey 1
controlkey 1
#
# Locate the drift file
#
driftfile /etc/ntp.drift
#
# We get disconnected every once in a while. If that happens, and we cannot
# talk to ANYONE, then our stratum ceiling is 11.
#
server 127.127.1.10
#
# We have a CHU modem
#
server 127.127.7.0
#
# We're pretty far from CHU, and we have a lousy (sun) system clock.
#
fudge 127.127.7.0 time1 0.013434 flag1 1

Is the stratum-ceiling driver (127.127.1.10) a good idea in this
configuration? What happens to xntpd when it has nobody to talk to?

At night, when news is being expired, I get quite a few 'previous
time adjustment didn't complete'. Would increasing tickadj help
things, or is that a bad idea?

Does anyone have any novel ideas on statistical analysis of some
of the data provided by xntpdc or ntpq? I have the sinking feeling
my setup isn't doing as well as I think it is...

-- 
Nick Sayer              | Think of me as a recombinant    | RIP: Mel Blanc
mrapple@quack.sac.ca.us | Simpson: Homer's looks, Lisa's  |   1908-1989
N6QQQ                   | brains, Bart's manners, and     |  May he never
209-952-5347 (Telebit)  | Maggie's appetite for TV.  --Me |  be silenced.