Quote from: Greg_E on May 27, 2026, 05:08:22 PMIt seems like limiting the threads would be more work than it's worth. Once the code base migrates to multi-thread, it seems like it would be worth just keeping that for all versions.I believe that you're not assessing this correctly. With that new architecture all versions of the engine would use a multicore design and the maximum number of parallel threads is just a number that can be changed. And for home subscriptions and non-paying users this number would simply be set to "1". So the only way to avoid the jerks using a home subscription for their company is to tie the maximum number of threads to the subscription. Sadly home users apparently won't benefit at all from the new design.
Quote from: meikel on Today at 08:31:06 AM* Today I learned ISC DCHP is so hard deprecated that it is not even backed up when you create a backup. It backups the config values but does not backup (now a plugin) ISC from what I could tell.
Quote from: Patrick M. Hausen on June 03, 2026, 11:34:11 AMSo funktioniert das nunmal.
Quote from: viragomann on June 03, 2026, 08:26:19 PMQuoteAufs Manangement-Interface würde der Traffic auch nicht kommen, davon war nicht die Rede.QuoteClients am LAN könnten eben so gut ihre DNS-Anfragen an die Management-IP richten. Wenn da ein DNS läuft und die Firewall-Regen den Zugriff erlauben, werden sie eine Antwort erhalten.
Sowas würde ich schon aus Prinzip nicht machen - Lan-Traffic hat am Management-Interface per se nichts zu suchen!
# cat /proc/cpuinfo
...
processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 154
model name : 12th Gen Intel(R) Core(TM) i3-1215U
stepping : 4
microcode : 0x43a
# dmesg | fgrep microcode
[ 0.964793] microcode: Current revision: 0x0000043a
[ 0.964796] microcode: Updated early from: 0x00000434