Agustín Dall'Alba
Agustín Dall'Alba
I confirm it works, and I see no side effects.
I could have added an `accept_enable()` in redsocks.c:1032, right before the `return`, but my reasoning was that the `accept_backoff_ev` event being pending "means" that redsocks isn't listening at the moment—and...
Works for me, #34 unnecesary. Edit: too bad I found this only after making my own patch.
I found the bug. There's a situation where the connection pressure is solved but redsocks doesn't resume listening to new connections. See #100 :) Edit: This of course doesn't solve...
 Example of the inconsistency.
There is one more missing header: `#include ` for `ntohl`.
`--namespace=caddy-system --set minikube=true --set replicaCount=1` is good enough for a 1-node cluster. You may delete the `LoadBalancer`-type Service. You might have to give the `caddy-system` namespace the label `pod-security.kubernetes.io/enforce: privileged`....
I image what's missing is the incremental send/recv for FILE and FILE_THIN. It would be possible to do by keeping the base snapshot in the filesystem and comparing physical addresses...
I'm having this issue as well. I'm encrypting all partitions, and I'm not sure if it's the cause but I also noticed that the `/var` partition is failing to `cryptsetup...
>* Wait for normal Pods to drain. Guess this is best handled by being a "critical pod". I agree, and this is already handled: both the satellite and csi-node Pods...