From owner-freebsd-stable Fri Jan 4 16:19:38 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vortex.wa4phy.net (cc449817-a.mrtnz1.ga.home.com [24.12.79.51]) by hub.freebsd.org (Postfix) with ESMTP id A935F37B41F for ; Fri, 4 Jan 2002 16:19:33 -0800 (PST) Received: from vortex.wa4phy.net (localhost.wa4phy.net [127.0.0.1]) by vortex.wa4phy.net (8.11.6/8.11.6) with ESMTP id g050JU873702; Fri, 4 Jan 2002 19:19:30 -0500 (EST) (envelope-from sam@wa4phy.net) Message-ID: <3C364692.57C3AF56@vortex.wa4phy.net> Date: Fri, 04 Jan 2002 19:19:30 -0500 From: Sam Drinkard Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-PRERELEASE i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: Doug White Cc: freebsd-stable@FreeBSD.ORG Subject: Re: systat message References: <20020104135233.G65848-100000@resnet.uoregon.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Actually, my problem was there was a copy of systat located in /bin, as well as a copy of most other files from /usr/bin. I have no idea how they got there, but I suspect most likely from a 3.4-R restore of stuff via tar. My best guess. I do know how to keep stuff in sync, albeit following directions is not my best trait... As I said, the problem is solved, along with several other items that created wierd events, all because of the files in /bin that shouldn't have been there to start with. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message