On 2013-01-25 08:46, USMCleather wrote:
> Mr. Velden,
> I believe what I will do is attempt to restate the process I have
> completed thus far with my - AMATEUR - attempt at making a home NTP
> server. I have no formal training with computers, operating system,
> etc.; so I am very much an amateur. I try to avoid the CLI when
> possible, unless I have step-by-step instructions of what to do; because
> I do know that you can really FUBAR your computer if you don’t know what
> your doing. So everything that I will attempt to explain has only
> happened in the GUI.
You can ruin a system also using the GUI :-p
Really, the CLI is the strongest point in favour of Linux. It is so much
easier to follow steps and keep track of them.
> Today I am attempting to create a new synchronization type by selecting
> Add > Radio Clock. My radio clock is a DeLorme Earthmate BT-20 (NMEA
> 2.0) GPS receiver. In the Local Reference Clock menu - under clock type
> - I select “Generic NMEA GPS Receiver.” Then I go to OK, which takes me
> back to the main “Advanced NTP Configuration”. Again I click OK so that
> the NTP settings take effect and re-start the ntpd daemon.
> I then will go back into the “Advanced NTP Configuration” and the I
> will select “Display Log”.
> The log output is: “24 Jan 23:15:47 ntpd: ntpd exiting on
> signal 15” - note1 = This I assume is good and is based on my Server
> Synch to the USNO
No, it says that it exits on signal 15, the program is told to
terminate. It has been killed.
SIGTERM 15 Term Termination signal
> “24 Jan 23:15:55 ntpd: refclock_open
> /dev/gps0: No such file or directory” - note2 = This is obviously the
> GPS, but the ntpd isn’t finding the GPS
> “24 Jan 23:15:55 ntpd: 127.127.20.0
> interface 127.0.0.1 -> (none)” - note3 = This I believe is in reference
> to the generic NMEA driver
> In reference to note2; I have used the udev-browse command to
> verify that my system is recognizing that my GPS is plugged in to my
> computer. It says that the GPS
> In the Local Reference Clock menu where it allows you to create a
> symlink; I have entered this information and it still results in the
> same log output.
I would like to read some documentation about you having to create any
> I hope that this has cleared up what I have been able to do so far.
> Now the question is: How do I trouble shoot and fix this issue so that
> ntpd will use my GPS as a clock reference?
I use ntp, but I never had the chance to test a GPS receiver and connect
it to a computer with ntpd. So I would have to read some documentation
on that… Perhaps you have to communicate on some specific ntpd forum
or mail list, but they will probably want you to use CLI.
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)