From: Keith Owens <kaos@ocs.com.au>
To: Taral <taral@taral.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/net/ip_conntrack problems
Date: Mon, 29 Oct 2001 15:27:52 +1100 [thread overview]
Message-ID: <3974.1004329672@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 28 Oct 2001 22:08:54 MDT." <20011028220854.A17685@taral.net>
On Sun, 28 Oct 2001 22:08:54 -0600,
Taral <taral@taral.net> wrote:
>% dd if=/proc/net/ip_conntrack bs=128 | wc -l
>0+0 records in
>0+0 records out
> 0
>% dd if=/proc/net/ip_conntrack bs=256 | wc -l
>0+3 records in
>0+3 records out
> 3
>Can anyone explain this? (2.4.13-ac3) It's wreaking havoc with my
>program.
Some /proc output is blocked, it will only return complete lines. If
your buffer is not big enough to hold the next line then you don't get
anything at all. Try cat /proc/net/ip_conntrack | wc.
next prev parent reply other threads:[~2001-10-29 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 4:08 /proc/net/ip_conntrack problems Taral
2001-10-29 4:27 ` Keith Owens [this message]
2001-10-29 4:36 ` Taral
2001-10-29 21:19 ` Mike Fedyk
2001-10-29 22:24 ` Taral
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=3974.1004329672@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=taral@taral.net \
/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