From nobody Sun May 28 09:22:48 2023 X-Original-To: freebsd-doc@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QTY9L1Grmz4Wryn for ; Sun, 28 May 2023 09:23:02 +0000 (UTC) (envelope-from wschnr@googlemail.com) Received: from mail-ej1-f43.google.com (mail-ej1-f43.google.com [209.85.218.43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QTY9K6N7gz3jx8 for ; Sun, 28 May 2023 09:23:01 +0000 (UTC) (envelope-from wschnr@googlemail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-f43.google.com with SMTP id a640c23a62f3a-96f6a9131fdso340941366b.1 for ; Sun, 28 May 2023 02:23:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685265780; x=1687857780; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CVv580JV826v/X9qGOouS8Ik7s+hETNx9uxmY4wmbt8=; b=VAMDb3HbLKo3Y4R+FW8OrayPalPeykVDKyn61AHnPv2UtRexS/LYVVF9ZIfPvRsXBb Y0Acf+qRKEdlxXD2uSmpdFzcRKdPcYGmt54GAnP7IqeXyw3RybDAGBvTx6YPAcL62z20 +CMTXtyrTsNcB4Wdy1905hoLJGF2EoeACo7BozsUb8c+gSnz/Yuuyt1i5oGJsaubpF4U Wwzt4aYYjqz4xLuN9axR0BV2uqSq2bTcWFsOMTb0x4OV3v5oaLMcrz4QSgd+P+AGP/fr Hzr5vO1igmquDUS0nGDS5Pc7tzI6ZBu5RvCtl/ks/8VfjBkpM92qTNW62TG0Y0kRmW7X C25w== X-Gm-Message-State: AC+VfDxKs8tvDPMmO+VKUvxtaaweIVNad32Q3sFYBbw1m67kKQygZHrQ IhuP0PAibdk0H2eUuRLF8mcClSQL8ioHAttnXMnac9bI2l0= X-Google-Smtp-Source: ACHHUZ6i0D3JTM7zpkyJ1EhIVqkSbF5GOblz8u/Oid3LT8FcvAHUCgdrvbfPt6zYyrmOC2W1z+ChKH9lz3x0d5Mjhh8= X-Received: by 2002:a17:907:2683:b0:971:2eaf:556 with SMTP id bn3-20020a170907268300b009712eaf0556mr6479204ejc.18.1685265780084; Sun, 28 May 2023 02:23:00 -0700 (PDT) List-Id: Documentation project List-Archive: https://lists.freebsd.org/archives/freebsd-doc List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-doc@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Wolfram Schneider Date: Sun, 28 May 2023 11:22:48 +0200 Message-ID: Subject: Re: Where is man.wrapper as used by website/content/en/cgi/man.cgi To: "Edward Sanford Sutton, III" Cc: freebsd-doc@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4QTY9K6N7gz3jx8 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Sat, 27 May 2023 at 21:51, Edward Sanford Sutton, III 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 https://wolfram.schneider.org