Date: Sat, 30 Oct 2010 22:00:41 -0700 From: perryh@pluto.rain.com To: wblock@wonkity.com, sterling@camdensoftware.com Cc: questions@freebsd.org Subject: Re: man(1) output error Message-ID: <4cccf7f9.0UgCkeA%2Bowm8JoKb%perryh@pluto.rain.com> In-Reply-To: <alpine.BSF.2.00.1010302050110.7006@wonkity.com> References: <alpine.BSF.2.00.1010282232340.58967@wonkity.com> <AANLkTimvdoceCoBhpiLGUkftLN0L=qfVV0nm_aD49kR7@mail.gmail.com> <20101029185853.0631917f.freebsd@edvax.de> <20101029184958.GE2439@libertas.local.camdensoftware.com> <alpine.BSF.2.00.1010301810530.6585@wonkity.com> <alpine.BSF.2.00.1010302050110.7006@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warren Block <wblock@wonkity.com> wrote: > >>> % man csh | less +/rehash > >>> [...] > >>> Error executing formatting or display command. > >>> system command exited with status 36096 > >>> Error executing formatting or display command. > >>> system command exited with status 36096 > >>> No manual entry for csh > >>> % ... > > This seems to be a problem with the csh man page. > > Other pages work fine, like 'man hosts | less +/named' > > or 'man devfs | less +/ruleset'. > > Actually, it appears to be a problem with long manual pages, > including csh, bash, or perlfunc. Does it by any chance go away if you cause "less" to read the pipe all the way to EOF, e.g. by entering G, before exiting? If so, there may be a problem in the way man handles SIGPIPE.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4cccf7f9.0UgCkeA%2Bowm8JoKb%perryh>