From: "David S. Miller" <davem@redhat.com>
To: "James H. Cloos Jr." <cloos@jhcloos.com>
Cc: netdev@oss.sgi.com
Subject: Re: tcp socket missing from /proc/net/tcp
Date: Sat, 23 Aug 2003 17:27:10 -0700 [thread overview]
Message-ID: <20030823172710.478f30f9.davem@redhat.com> (raw)
In-Reply-To: <m3lltk17er.fsf@lugabout.jhcloos.org>
On 23 Aug 2003 15:49:16 -0400
"James H. Cloos Jr." <cloos@jhcloos.com> wrote:
> I've currently got an open ssh session to a remote box that does not
> show up in /proc/net/tcp (I also checked /proc/net/tcp6 even though
> the remote box doesn't do v6; it is not there either).
Not surprising, nothing seems to be initializing
net/ipv6/tcp_ipv6.c:tcp6_seq_fops
I'd welcome patches to fix this.
next prev parent reply other threads:[~2003-08-24 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 19:49 tcp socket missing from /proc/net/tcp James H. Cloos Jr.
2003-08-24 0:27 ` David S. Miller [this message]
2003-08-24 1:07 ` YOSHIFUJI Hideaki / 吉藤英明
2003-08-24 4:20 ` David S. Miller
2003-08-27 5:41 ` James H. Cloos Jr.
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=20030823172710.478f30f9.davem@redhat.com \
--to=davem@redhat.com \
--cc=cloos@jhcloos.com \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).