eldritch horrors
289fab6a68
it's used very rarely, on ssh it's pretty much broken, and on ssh-ng it's standing squarely in the way of the rpc transition. we have not found significant use of this feature in public configs (with all of *two* repositories using this store parameter), so why even keep it? Change-Id: Ifcafdf794d815001a1a55a771e5823010e5b174b
547 B
547 B
synopsis, cls, category, credits
| synopsis | cls | category | credits | |
|---|---|---|---|---|
| Remove `max-connections` store parameters for `ssh://` and `ssh-ng://` stores | Miscellany |
|
The max-connections parameter was undocumented, untested, and (in the case of ssh) even ignored
entirely for remote builds. During a survey of public nixos configurations we have found two uses
of max-connections for ssh-ng, and none at all for ssh. Since it is so rarely used but brings
significant internal complexity that hinders improvements we have decided to remove these features.