Closed osctobe closed 1 year ago
I like this change. That would be also useful for containers I think. It needs additional changes in cr-service.c
I think and I also think that the name NETWORK_LOCK_DUMMY
is not the best choice. Maybe a name that includes NO_LOCK
or so would be better.
I like this change. That would be also useful for containers I think. It needs additional changes in
cr-service.c
I think
Done.
and I also think that the name
NETWORK_LOCK_DUMMY
is not the best choice. Maybe a name that includesNO_LOCK
or so would be better.
Can we have more votes on the name? I think NETWORK_LOCK_DUMMY reads better than NETWORK_LOCK_NO_LOCK, unless we're willing to have NETWORK_NO_LOCK or similar.
Would NONE instead of DUMMY be better? (Keeping it a single-word.)
Would NONE instead of DUMMY be better? (Keeping it a single-word.)
NETWORK_LOCK_NONE
looks better. It is similar to the --manage-cgroups none
option.
Make it possible to skip network lock to enable uses that break connections anyway to work without iptables/nftables being present.
How does this option relate to --tcp-close
? Should these two options be used together?
Make it possible to skip network lock to enable uses that break connections anyway to work without iptables/nftables being present.
How does this option relate to
--tcp-close
? Should these two options be used together?
It makes --tcp-close
cheaper. Added a hint to the doc.
Patch coverage: 14.28
% and project coverage change: -0.02
:warning:
Comparison is base (
9301aba
) 70.71% compared to head (5e265a5
) 70.69%.:exclamation: Current head 5e265a5 differs from pull request most recent head da85519. Consider uploading reports for the commit da85519 to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Make it possible to skip network lock to enable uses that break connections anyway to work without iptables/nftables being present. This is used in Google's environment where we drop all connections and reconnect after migration.