mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bodo Eggert <7eggert@gmx.de>
To: John Schmerge <schmerge@speakeasy.net>
Cc: 7eggert@gmx.de, linux-kernel@vger.kernel.org
Subject: Re: Question regarding /proc/<pid>/fd and pipes
Date: Thu, 9 Feb 2006 10:02:44 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.58.0602090959450.2152@be1.lrz> (raw)
In-Reply-To: <Pine.LNX.4.58.0602081912160.25842@shell3.speakeasy.net>

On Wed, 8 Feb 2006, John Schmerge wrote:

> Thanks for the answer... I've got one more question: will the symlinks
> to the pipe be the same for both the read and write ends in all
> processes sharing the pipe?

It seems like yes. You can find it out by sinply trying it out.

> I've got some sort of funky race condition occurring between the read
> from the pipe and the exiting of the process on the write-end of the pipe...
> The read-process is supposed to exit after the write-process finishes
> (and does in about 1/2 the time), but I think I'm seeing the read-process
> blocked by something even after the write-process completes... Both top
> and ps give no indication that the read-process is blocked on a read(2).
> I've got some digging to do, but I'm thinking that this might actually be
> a kernel bug.

Do you close() the writing end in the process that's supposed to read?
-- 
Top 100 things you don't want the sysadmin to say:
98. What the hell!?

  reply	other threads:[~2006-02-09  9:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5DRW7-322-1@gated-at.bofh.it>
2006-02-08 14:45 ` Bodo Eggert
2006-02-09  3:22   ` John Schmerge
2006-02-09  9:02     ` Bodo Eggert [this message]
2006-02-09 17:21   ` Jan Engelhardt
2006-02-08  7:27 John Schmerge

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=Pine.LNX.4.58.0602090959450.2152@be1.lrz \
    --to=7eggert@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schmerge@speakeasy.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

all inboxes | Powered by JetHome®