Steve Kostecke wrote: > On 2008-12-13, Varrun Ashok <[email protected]> wrote: > >> I have a serious problem while running ntpd-4.2.4p4. While i type ntpd >> -D 3 it says wildcard interface #0 0.0.0.0 disabled. Is this wrong or >> the right message? > > It don't have that version installed any where, but I believe that is > correct.
That is correct. It really means that any packet arriving on that interface will be dropped. It will pick up packets on the other interfaces. You shouldn't have any interfaces besides the enumerated ones so nothing should arrive on that interface. > >> then i kill ntpd >> then i restart it and type ntpq -p >> the table headings appear but nothing appears beneath it > > What is in your ntp.conf? > >> when i do a ps -ef i realize that ntpd has been killed automatically >> as soon as i run ntpq -p. > > I've never heard of 'ntpq -p' killing a running ntpd process. That's not what's happening. If ntpd were not running you'd get a "connection refused" message. You simply haven't waited long enough for ntpd to synchronize. > >> then i try ntpd and then ntpdc -p >> under the field(column) local both the addresses mentioned are 127.0.0.1! That probably means that you configure ntpd to point to itself as a server which is wrong. (We should be rejecting such a configuration anyway). > > If ntpdc -p works so should ntpq -p. > >> actually i am using a gps clock and ntpq -p must give me 0.0.0.0 in >> the row showing GPS details. A gps must be configured in order to be used. The wildcard interface is NOT used for that. Danny _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
