From owner-freebsd-questions@FreeBSD.ORG Sun Sep 21 11:37:56 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C65E16A4B3 for ; Sun, 21 Sep 2003 11:37:56 -0700 (PDT) Received: from smtp.volant.org (gate.volant.org [207.111.218.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE64143F3F for ; Sun, 21 Sep 2003 11:37:54 -0700 (PDT) (envelope-from patl+freebsd@volant.org) Received: from 64-144-229-193.client.dsl.net ([64.144.229.193] helo=[192.168.0.13]) by smtp.volant.org with asmtp (TLSv1:AES256-SHA:256) (Exim 4.22) id 1A195l-000Hb0-9Q for questions@freebsd.org; Sun, 21 Sep 2003 11:37:53 -0700 Date: Sun, 21 Sep 2003 11:37:50 -0700 From: Pat Lashley To: questions@freebsd.org Message-ID: <2088603520.1064169470@mccaffrey.phoenix.volant.org> X-Mailer: Mulberry/3.1.0b6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Scan-Signature: ccec3068c2c34a412b04326b5f6d3453a40553ac X-Spam-Score: 0.3 (/) X-Spam-Score-Int: 3 X-Spam-Report: 0.3/5.0 This mail has matched the spam-filter tests listed below. See http://spamassassin.org/tag/ for details about the specific tests reported. In general, the higher the number of total points, the more likely that it actually is spam. (The 'required' number of points listed below is the arbitrary number above which the message is normally considered spam.) Content analysis details: (0.30 points total, 5 required) AWL (0.3 points) AWL: Auto-whitelist adjustment Subject: ntop: Bad file descriptor on device 1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 18:37:56 -0000 I've just installed the ntop port, on a 4.8-STABLE system that has two NICs. When I run ntop, it always gives me this error: **ERROR** Reading packets on device 1(sis0): 'read: Bad file descriptor' In this case sis0 is the second NIC listed. If I swap the order in the -i option, it will report the error on '...device 1(sis1)...' In either case, it does not report any data for that NIC. My ports directory is up to date; but the -STABLE system was last cvsupp'd and built on 25 April. Any clues what might be causing this or how to fix it? Thanks, -Pat