From owner-freebsd-questions@FreeBSD.ORG Thu Nov 6 10:52:30 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 57B0416A4CE for ; Thu, 6 Nov 2003 10:52:30 -0800 (PST) Received: from forrie.com (forrie.ne.client2.attbi.com [24.147.156.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 490D043FE3 for ; Thu, 6 Nov 2003 10:52:27 -0800 (PST) (envelope-from forrie@forrie.com) Received: from dell.forrie.com (wks.forrie.net. [192.168.1.21]) by forrie.com with ESMTP id hA6IqAAJ067221 for ; Thu, 6 Nov 2003 13:52:12 -0500 (EST) (envelope-from forrie@forrie.com) Message-Id: <6.0.0.22.2.20031106134936.01f376c8@192.168.1.1> X-Sender: forrie@192.168.1.1 X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Thu, 06 Nov 2003 13:52:10 -0500 To: freebsd-questions@freebsd.org From: Forrest Aldrich Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean Subject: Trouble using the "man" subsystem 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: Thu, 06 Nov 2003 18:52:30 -0000 I posted about this a while ago. For some time, I've had a broken manpage system on my FreeBSB box. Currently, it's at FreeBSD-4.9. The symptoms are: sometimes I get an error about not being able to locate tmac for tty-char. Though I can find that in /usr/local/share/groff, etc. Most times, I will do "man command" and the prompt just returns. Nothing, nada. I'm absolutely puzzled, because a reinstall (makeworld/buildworld) does NOT resolve the problem. I cannot see there to be any odd environment variables, however this suggests there may be a configuration issue "somewhere". I'm out of ideas, and wonder if anyone out there has suggestions about where to look, how to fix this. Thanks, Forrest