From: paurea@plan9.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] events
Date: Wed, 19 Feb 2003 15:31:19 +0100 [thread overview]
Message-ID: <8e8e29794814dcea619f959a1114a727@plan9.escet.urjc.es> (raw)
In-Reply-To: <9a6a6d2af56b7f808af4057c6d501fc9@plan9.bell-labs.com>
> While the program is sitting there doing nothing,
> you can cat its /proc/pid/fd file to see what the
> read offset on the pipe is -- that will tell you
> whether the slave process has read any data
> from the pipe. If not, your generator program is
> not generating.
The data is getting there. I have already checked. I have run
tail -f /tmp/b|goifc on one terminal and
cat >/tmp/b
on another and cat /proc/pid/fd and seen that the |data offset increased.
But nothing got printed. Also changed the print for an exits just in case
something was not getting flushed. Doesn't work either.
Gorka
next prev parent reply other threads:[~2003-02-19 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 13:23 paurea
2003-02-19 13:56 ` Russ Cox
2003-02-19 14:08 ` paurea
2003-02-19 14:13 ` Russ Cox
2003-02-19 14:31 ` paurea [this message]
2003-02-19 21:57 ` Russ Cox
2003-02-20 11:18 ` paurea
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 13:20 paurea
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=8e8e29794814dcea619f959a1114a727@plan9.escet.urjc.es \
--to=paurea@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/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).