136 reputation
5
bio website
location
age
visits member for 3 years, 9 months
seen Sep 10 '13 at 15:34
Your basic geek computer science dork. Interested in learning about compilers, AI, machine learning, and software architecture. Enjoys programming embedded systems.

Dec
4
awarded  Popular Question
Jul
16
awarded  Commentator
Jul
16
comment Single NTP server on isolate network
to create a driftfile and I can see its contents (44.025 after running all weekend), but this alone was not enough to get a fast synch. The restarting of ntp seems to be the key.
Jul
16
comment Single NTP server on isolate network
+1 from me for your effort, but it's not solving my problem. A solution I've found (and please suggest something else if you wish and I'll try it) is to kill ntpd on machine A after it synchs to the GPS, and then restart it. This seems to let machine B synch to machine A within seconds. My guess is that a 42-year jump in time on Machine A (always boots from the Epoch) is making it nervous about sharing its time, but when it starts and the clock is already set, it's as though the clock wasn't far off to being with, so minor adjustments make it feel good about sharing its time. I did allow ntp..
Jul
13
comment Single NTP server on isolate network
Perhaps this is an issue due to the driftfile not being created?
Jul
13
revised Single NTP server on isolate network
added 1191 characters in body
Jul
13
revised Single NTP server on isolate network
added 1 characters in body
Jul
13
comment Single NTP server on isolate network
Also, if you get a chance to edit your answer again, could you @ me so the system notifies me? Thanks.
Jul
13
comment Single NTP server on isolate network
I actually made one small mistake, I already had the full version of ntpd running on Machine A. Machine B is the only one running the BusyBox version (and if I had a way to build programs for it, I'd do the same there). Eventually, everything works. I think it's a sever trust problem. Could you give some insight to my edits? Thanks.
Jul
13
revised Single NTP server on isolate network
added 724 characters in body
Jul
13
comment Single NTP server on isolate network
Adding burst to the conf file did not improve the situation. Each of these machines is a busybox machine, and the "-c" option is unknown to ntpq. Also, the clocks cannot be trust on these devices until they are synched with the GPS. Just a limitation of the systems. Thanks.
Jul
13
revised Single NTP server on isolate network
deleted 3 characters in body
Jul
13
awarded  Editor
Jul
13
comment Single NTP server on isolate network
@AaronCopley Updated.
Jul
13
revised Single NTP server on isolate network
added 373 characters in body
Jul
12
comment Single NTP server on isolate network
@DavidSchwartz Thanks. I'll look into it, but I'm a little reluctant to change much beyond configurations if I can help it. It's a chore to cross-build anything for Machine B at this time.
Jul
12
comment Single NTP server on isolate network
@AaronCopley I can post those in a few (10 or 12) hours. Machine A becomes sychronized to the GPS within a minute of booting Machine B has problems synching to machine A for quite a long period of time.
Jul
12
awarded  Student
Jul
12
asked Single NTP server on isolate network
Nov
11
comment Networks, subnets, routing and NAT
@ninjali In my poor wording, that's what I was getting at. Thanks.