This is why yesterday I separated out the radicle-node instance from the radicle-httpd instance.
The radicle-node instance is the #HardenedBSD primary seed node. That node also performs our every-six-hour autosync with #FreeBSD.
The Radicle httpd (radicle-httpd) provides a web-accessible read-only view of our various projects. The httpd will create as many new threads as requests that come in. It has no upper bounds.
This means that I need to place those bounds via other means, like applying resource constraints to the jail.
If both the node and the httpd are running in the same jail, a threat actor could just spawn a bunch of long-running web requests, which would prevent our autosync from succeeding.
So, now that the node and the httpd are separate, we can still have a reliable autosync while having a less-reliable read-only httpd.