Bodo,
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?
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.
Thanks,
John
On Wed, 8 Feb 2006, Bodo Eggert wrote:
> John Schmerge <[email protected]> wrote:
>
> > I know that the symlinks in the /proc/<pid>/fd directory point to
> > bogus filenames for pipes (i.e. 'pipe:[64682]') and am wondering if
> > every process that reads and writes from that pipe will share the same
> > bogus symlink name.
>
> yes
>
> > In essence, I'm wondering if there's any way to list all of the pid's
> > of processes using an anonomous pipe.
>
> man find. I don't know a bettre way.
> --
> Ich danke GMX daf�r, die Verwendung meiner Adressen mittels per SPF
> verbreiteten L�gen zu sabotieren.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
