Thanks -- I learned something.
My goal is to call ( *roff ) , and then catch , and display the man-page
in perlman.
I want this because of the probs I have with mwm.1 .
I currently use 'rman' (also in pkgsrc)
On Sat, Jun 17, 2023 at 10:41 PM Robert Elz wrote:
>
> Date:Sat, 17 Jun
Date:Sat, 17 Jun 2023 15:18:35 +
From:Todd Gruhn
Message-ID:
| This works:
| groff -man /usr/pkg/man/man1/man.1 -Tascii 2> /dev/null | more
I'm surprised, I would have expected it to need to be
groff -man -Tascii /usr/pkg/man/man1/man.1
Want to view mwm.1 -- some stuff does not show correctly.
This works:
groff -man /usr/pkg/man/man1/man.1 -Tascii 2> /dev/null | more
FAIL:
groff -man man.1 -Tascii 2> /dev/null | more
WHY? Is there a $VAR that needs to be set ?
OR , does 'groff -man ...' always need to have
mlel...@serpens.de (Michael van Elst) writes:
> Fastly caches data in segments:
>
> https://docs.fastly.com/en/guides/segmented-caching
>
> If some segments of a file can be fetched from the backend
> and others cannot, fastly will deliver a partial file and
> return an error. For a complete file
riastr...@netbsd.org (Taylor R Campbell) writes:
>We've been hearing reports of intermittent issues with broken partial
>downloads via our content delivery network, Fastly, from
>cdn.NetBSD.org, nycdn.NetBSD.org, and/or archive.NetBSD.org,
>particularly of large files like the installer images.
> Date: Sat, 17 Jun 2023 10:24:26 +
> From: Taylor R Campbell
>
> So if you catch a partially failed download with, e.g.,
>
> curl -H 'Fastly-Debug: true' -D header.txt -O https://archive.NetBSD.org/...
>
> then it would be helpful to us if you could pass on the header.txt
> file that curl
Hi folks,
We've been hearing reports of intermittent issues with broken partial
downloads via our content delivery network, Fastly, from
cdn.NetBSD.org, nycdn.NetBSD.org, and/or archive.NetBSD.org,
particularly of large files like the installer images.
These issues are hard to track down because
