> On Sun, 25 Feb 2024, at 16:14, S.N.Grigoriev wrote:
>
>>> Another thing maybe worthwhile trying is to just have that one thing
>>> plugged into the usb subsystem. Beforehand, tail -f /var/log/messages
>>> in an xterm, unplug everything usb (2&3), plug in the cd drive,
>>> observe messages.
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The first RC build of the 13.3-RELEASE release cycle is now available.
Installation images are available for:
o 13.3-RC1 amd64 GENERIC
o 13.3-RC1 i386 GENERIC
o 13.3-RC1 powerpc GENERIC
o 13.3-RC1 powerpc64 GENERIC64
o 13.3-RC1 powerpc64le GENERIC6
Currently trying to do port builds with
poudriere-devel-3.4.99.20240122 on 13.3-STABLE FreeBSD 13.3-STABLE
stable/13-n257396-134580c103b4 GENERIC amd64 and have had poor system
responsiveness on this and a -STABLE that was likely at least 2 months
before it with `/usr/bin/nice -n 18 /usr/sbin
While building a bunch of ports under 13.3-RC1 I find that libpfctl does
not (build). I freely admit I do not understand how this port works; I
started to create a PR but I don't have the first idea on how the
distfile is generated.
Meanwhile 1136 other ports built for me without issue.
On 2/26/24 18:04, Craig Leres wrote:
While building a bunch of ports under 13.3-RC1 I find that libpfctl does
not (build). I freely admit I do not understand how this port works; I
started to create a PR but I don't have the first idea on how the
distfile is generated.
`make makesum` or hand
On 2/26/2024 5:07 PM, Edward Sanford Sutton, III wrote:
While building a bunch of ports under 13.3-RC1 I find that libpfctl does
not (build). I freely admit I do not understand how this port works; I
started to create a PR but I don't have the first idea on how the
distfile is generated.
`mak
On 2/26/24 18:19, Craig Leres wrote:
On 2/26/2024 5:07 PM, Edward Sanford Sutton, III wrote:
While building a bunch of ports under 13.3-RC1 I find that libpfctl does
not (build). I freely admit I do not understand how this port works;
I started to create a PR but I don't have the first idea on
Given the complexity of your situation, a combination of adjustments might be
necessary to find a balance that works for your specific needs. It's often a
process of trial and error, tweaking one setting at a time and observing the
impact on your system's performance and responsiveness.
The iss
Questions include (generic list for reference,
even if some has been specified):
For /boot/loader.conf (for example) :
What value of sysctl vm.pageout_oom_seq is in use?
This indirectly adjusts the delay before sustained
low free RAM leads to killing processes. Default 12
but 120 is what I use
