From owner-freebsd-hackers Wed Apr 23 19:24:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA09758 for hackers-outgoing; Wed, 23 Apr 1997 19:24:13 -0700 (PDT) Received: from iceberg.anchorage.net. (root@iceberg.anchorage.net [207.14.72.150]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA09752 for ; Wed, 23 Apr 1997 19:24:09 -0700 (PDT) Received: from iceberg (iceberg [207.14.72.150]) by iceberg.anchorage.net. (8.6.11/8.7.3) with SMTP id RAA04459; Wed, 23 Apr 1997 17:20:12 -0800 Date: Wed, 23 Apr 1997 17:20:12 -0800 (AKDT) From: un_x X-Sender: un_x@iceberg To: David Nugent cc: freebsd-hackers Subject: Re: manpages In-Reply-To: <199704240136.LAA22333@unique.usn.blaze.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 24 Apr 1997, David Nugent wrote: > > > > can anyone tell me how i might get manpages to work? > > > > > > /usr/share/man/cat* should be owned by man.bin, mode 755 > > > /usr/bin/man should be owned by man.bin, mode 4555 (-r-sr-xr-x) > > > > yes - that is correct, my problem is that something is translating > > my manpages into non-gzip catpages. i can go in as root and > > cannot gzip -d any catpages. though they end in .gz and > > look ok. when executing a man command, zcat fails trying > > to unzip the cat page "not in gzip format". > > > > this is a fresh install of 2.2.1, for the 2nd time. > > i still have this problem. what's funny, is some > > pages that worked the 1st time, are not working now! > > only a VERY few. < 2%. > > When you format a manpage for the first time, is there an error > issued? Unfortunately, some machines are so damn quick it is > difficult to even see the message, let alone read it! :-) yes - zcat "not in gzip format" - and that all. additionally, mc (Midnight Commander) can read all my manpages just fine. > This sounds like a resource problem, though. What is your > MAX_CHILD setting? It's just that when fooling around with the default w/2.2.1. > resource limits in current and pre-2.2 release code I found > that anything less than ~24 file descriptors will cause man > to become disfunctional in exactly the way you describe. > Subsequently typing "man" for a (now) formatted page results > in either nothing or an error. > Check resource limits at the shell prompt with the ulimit > (sh) or limit (csh) command. If the hard limits are set too > low, you'll have to recompile your kernel. ulimit = unlimited ... > Regards, any relation to Ted? :) > David Nugent - Unique Computing Pty Ltd - Melbourne, Australia > Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet > davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ ------------------------------------------------------------------------------ Sleep: a sign a caffeine deprivation ... http://www.anchorage.net/~un_x ------------------------------------------------------------------------------