From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 8 03:31:56 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E08616A4BF for ; Mon, 8 Sep 2003 03:31:56 -0700 (PDT) Received: from smtp-relay2.barrysworld.com (smtp-relay2.barrysworld.com [213.221.172.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45A6443FEC for ; Mon, 8 Sep 2003 03:31:55 -0700 (PDT) (envelope-from killing@barrysworld.com) Received: from [213.221.181.50] (helo=barrysworld.com) by smtp-relay2.barrysworld.com with esmtp (Exim 4.22) id 19wJJD-0002u6-3j for hackers@freebsd.org; Mon, 08 Sep 2003 11:31:47 +0100 Received: from vader [212.135.219.179] by barrysworld.com with ESMTP (SMTPD32-7.15) id AB8F1E4800D4; Mon, 08 Sep 2003 11:35:59 +0100 Message-ID: <00a301c375f4$66080ee0$b3db87d4@vader> From: "Steven Hartland" To: References: <20030907233940.M18589@woozle.rinet.ru><3F5BB991.2050601@netli.com> <20030908113632.R55683@woozle.rinet.ru><3F5C3549.8050607@netli.com> <20030908120036.V55683@woozle.rinet.ru> <3F5C39B3.2010001@netli.com> Date: Mon, 8 Sep 2003 11:31:43 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: linprocfs issues X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Steven Hartland List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2003 10:31:56 -0000 For some strange reason linprocfs will mount multiple times to show this ensure you have the entry in fstab and then mount -a; mount -a You will now see 2 entries via df for linprocfs. Also it seems that linprocfs relies on procfs being mounted however I cant find any docs that mention this and see no reason why it should be the case. The problem I see is that I get errors from linux apps about /proc//file not existing. When trussing them they are never trying to open "file" I suspect it is happening when the access either cmdline or exe most likely exe. Steve / K