Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161060AbWBHH1J (ORCPT ); Wed, 8 Feb 2006 02:27:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161069AbWBHH1J (ORCPT ); Wed, 8 Feb 2006 02:27:09 -0500 Received: from mail4.sea5.speakeasy.net ([69.17.117.6]:38093 "EHLO mail4.sea5.speakeasy.net") by vger.kernel.org with ESMTP id S1161060AbWBHH1I (ORCPT ); Wed, 8 Feb 2006 02:27:08 -0500 Date: Tue, 7 Feb 2006 23:27:01 -0800 (PST) From: John Schmerge To: linux-kernel@vger.kernel.org Subject: Question regarding /proc//fd and pipes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1224 Lines: 29 Hi all, I'm attempting to track down a spooky problem with some code that I've written (running under the 2.6.11.12 kernel) and am wondering if there's a way to track (via /proc) both ends of an open pipe that was created with a pipe(2) system call... It appears that I've got a bunch of spawned processes stuck in some kind of sleep caused by a read(2) on the read-end of a pipe and would like to eliminate the possibility that I've done something truly bone-headed in my code like leaving the write-end of the pipe open in another process. (I don't think I did, but want to be sure :). I know that the symlinks in the /proc//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. In essence, I'm wondering if there's any way to list all of the pid's of processes using an anonomous pipe. Please CC me on any answers. Thanks, John - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/