From owner-freebsd-stable@FreeBSD.ORG Sun Jun 27 21:59:34 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7D4916A4CE for ; Sun, 27 Jun 2004 21:59:34 +0000 (GMT) Received: from lora.pns.networktel.net (lora.pns.networktel.net [216.83.236.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BB0743D1D for ; Sun, 27 Jun 2004 21:59:34 +0000 (GMT) (envelope-from phill@sysctl.net) Received: from MESE (wifi-ipnet.sysctl.net [216.83.242.102]) i5RH060Q001634 for ; Sun, 27 Jun 2004 17:00:06 GMT (envelope-from phill@sysctl.net) From: "Phillip Salzman" To: Date: Sun, 27 Jun 2004 16:59:35 -0500 Message-ID: <020c01c45c92$095b3750$6745a8c0@MESE> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal X-AntiVirus: checked by Vexira Milter 1.0.6; VAE 6.26.0.3; VDF 6.26.0.7 Subject: ``top'' and other process issues on 4.10-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jun 2004 21:59:35 -0000 Hello, I'm running a Dell 2650 2x3.2Ghz box with HTT disabled (the sysctl variable hasn't been set, so the user procs aren't taking advantage of the logical CPUs) & am seeing some rather strange issues with stdout processes. When I run a tail -f on my maillog (fairly active) I'm getting this intermittently: tail: stdout: Unknown error: 0 Also, vi doesn't seem to work anymore. It's giving me a ``Resource Not Available'' error most of the time I'm using it. This occurs both on remote SSH sessions and console. The boxes load hasn't gone over 1, but it is fairly active running some Vexira AV Milter software on as a mail gateway. I was seeing this same thing on a 5.2.1-R box but passed it off as a 5.2.1 issue. I'm using the same AV software on the 4.10 box as on the 5.2.1, but the 5.2.1 also seemed to have some issues with keeping sockets open in VexiraAV. Has anyone else seen this recently or have any recommendations? -- Phillip Salzman http://www.sysctl.net/phill/