From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jan Hinnerk Stosch <janhinnerk.stosch@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: regression when connecting to ipv6 localhost
Date: Sun, 14 Oct 2012 22:25:14 +0200 [thread overview]
Message-ID: <1350246314.21172.17139.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAO_aot7wZAqqQForAe-9aLnALqm1LdeaEv+ZKqiw3V_DCfqjRw@mail.gmail.com>
On Sun, 2012-10-14 at 21:57 +0200, Jan Hinnerk Stosch wrote:
> 2012/10/14 Eric Dumazet <eric.dumazet@gmail.com>:
> > On Sun, 2012-10-14 at 21:48 +0200, Jan Hinnerk Stosch wrote:
> >
> >> ntp.conf is (without comments):
> >> server fritz.box iburst
> >> restrict default noquery nopeer nomodify
> >> restrict 127.0.0.1
> >> restrict ::1
> >> driftfile /var/lib/ntp/ntp.drift
> >> logfile /var/log/ntp.log
> >>
> >> "lsof -p `pidof ntpd`" gives nothing
> >>
> >> and "ntpq -p ::1" results in the same timeout error "::1: timed out,
> >> nothing received
> >> ***Request timed out".
> >
> > So your ntpd is not running ?
> >
> > ps aux | grep ntpd
> >
> >
> >
>
> No, of course it is running:
> ntp 368 0.0 0.0 31288 2128 ? Ss 16:51 0:00
> /usr/bin/ntpd -g -u ntp:ntp
Hmm
pidof ntpd
should give you the pid of ntpd process : 368
So try
lsof -p 368 # instead of lsof -p `pidof ntpd`
next prev parent reply other threads:[~2012-10-14 20:25 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 15:38 regression when connecting to ipv6 localhost Jan Hinnerk Stosch
2012-10-14 19:29 ` Eric Dumazet
2012-10-14 19:48 ` Jan Hinnerk Stosch
2012-10-14 19:54 ` Eric Dumazet
2012-10-14 19:57 ` Jan Hinnerk Stosch
2012-10-14 20:25 ` Eric Dumazet [this message]
2012-10-14 20:26 ` Eric Dumazet
2012-10-14 20:28 ` Eric Dumazet
2012-10-14 20:39 ` Jan Hinnerk Stosch
2012-10-14 20:45 ` Eric Dumazet
2012-10-14 20:47 ` Eric Dumazet
2012-10-14 20:56 ` Jan Hinnerk Stosch
2012-10-14 21:02 ` Eric Dumazet
2012-10-14 21:07 ` Eric Dumazet
2012-10-14 21:21 ` Jan Hinnerk Stosch
2012-10-14 21:35 ` Eric Dumazet
2012-10-14 21:54 ` Jan Hinnerk Stosch
2012-10-14 22:01 ` Eric Dumazet
2012-10-14 22:11 ` Jan Hinnerk Stosch
2012-10-15 5:42 ` Eric Dumazet
2012-10-15 7:03 ` Jan Hinnerk Stosch
2012-10-15 7:14 ` Joe Perches
2012-10-15 7:39 ` Eric Dumazet
2012-10-15 7:43 ` Eric Dumazet
2012-10-15 11:25 ` Joe Perches
2012-10-15 12:31 ` Eric Dumazet
2012-10-15 13:10 ` Jan Hinnerk Stosch
2012-10-15 13:21 ` Eric Dumazet
2012-10-15 13:28 ` Jan Hinnerk Stosch
2012-10-16 16:07 ` Jan Hinnerk Stosch
2012-10-16 16:43 ` Eric Dumazet
2012-10-16 16:55 ` Eric Dumazet
2012-10-16 17:37 ` [PATCH] ipv6: addrconf: fix /proc/net/if_inet6 Eric Dumazet
2012-10-16 18:30 ` Jan Hinnerk Stosch
2012-10-16 18:39 ` David Miller
2012-10-16 22:01 ` Joe Perches
2012-10-16 18:55 ` David Miller
2012-10-15 9:25 ` regression when connecting to ipv6 localhost Eric Dumazet
2012-10-15 10:32 ` Jan Hinnerk Stosch
2012-10-15 9:07 ` Jan Ceuleers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1350246314.21172.17139.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=janhinnerk.stosch@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox