Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 May 2023 11:22:48 +0200
From:      Wolfram Schneider <wosch@freebsd.org>
To:        "Edward Sanford Sutton, III" <mirror176@hotmail.com>
Cc:        freebsd-doc@freebsd.org
Subject:   Re: Where is man.wrapper as used by website/content/en/cgi/man.cgi
Message-ID:  <CAMWY7CCH3yopGwW8PgNWvOfxTOCturVXcWWYSCC1y0C9uZbvAQ@mail.gmail.com>
In-Reply-To: <CO1PR11MB477063E48F59CCD12B03EA9CE6449@CO1PR11MB4770.namprd11.prod.outlook.com>
References:  <CO1PR11MB47705050837ECEC33AF89130E6449@CO1PR11MB4770.namprd11.prod.outlook.com> <CO1PR11MB477063E48F59CCD12B03EA9CE6449@CO1PR11MB4770.namprd11.prod.outlook.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 27 May 2023 at 21:51, Edward Sanford Sutton, III
<mirror176@hotmail.com> wrote:
>
>    In trying to troubleshoot tabs replacing spaces on manpages found on
> FreeBSD's website. As it isn't an issue in the original manpage, it
> seems to be involved in how the webpage versions are created. They
> aren't found or created in the documentation project build steps but a
> running web server creates them on the spot by running
> doc/website/content/en/cgi/man.cgi. Within that script it tries to
> execute man.wrapper which I have been unable to find. Anyone know where
> I can get or make a copy of it or what else I may have been doing wrong
> to get the cgi script going?

man.wrapper is a shell script which sets CPU time and memory limits to
kill endless  running groff processes. After setting the limits, the
script calls the man(1) script.

It is unclear why groff sometimes runs into an endless loop or uses
too much memory. Anyway, if you run a public service you must set some
limits to avoid DoS attacks.

-Wolfram

>    The issue seems to be related to every time 1+ spaces end at a
> tabstop, they are all replaced with a tab for PR #s 269214, 266433,
> 262225. I'd say either only use it at the start of a line with multiple
> spaces adding up to tabstops and end it when other characters are
> reached or better yet don't do it at all.
>    Another thing I have seen but not yet sure why is that the hyphen
> between an initial command and its description is turned into a double
> hyphen though I am not sure why.
> Thanks,
> Edward Sanford Sutton, III
>


-- 
Wolfram Schneider <wosch@FreeBSD.org> https://wolfram.schneider.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMWY7CCH3yopGwW8PgNWvOfxTOCturVXcWWYSCC1y0C9uZbvAQ>