On Sat, Jan 31, 2009 at 04:15:48PM -0600, Vince Mulhollon wrote: > On Sat, Jan 31, 2009 at 07:46:58PM +0100, Kurt Roeckx wrote: > > How do you expect "ntpq" to connect to localhost when you didn't > > configure it? Note that the manpage clearly states that > > localhost is the default. > > OK maybe my bug report was not so well written. Sorry about that. > > If ntpd can not be contacted by ntpq, perhaps because of "/etc/init.d/ntp > stop" then you get the following error from ntpq when it can not reach > ntpd: > ntpq: read: Connection refused
Here you have a route to localhost, and it replies that it can't connect. > > I am familiar with that error message. > > On the other hand, if ntpd is up and running perfectly, but interface lo is > down, such as "ifdown lo", then you get the following error from ntpq when > it can not reach ntpd: > localhost: timed out, nothing received > ***Request timed out. I'm guessing here you don't have a route to localhost, it gets send to your default gateway, and nothing replies. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
