diff for duplicates of <20210628220241.64f9af54@playground> diff --git a/a/content_digest b/N1/content_digest index ca9ef02..e0d985d 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -15,7 +15,7 @@ "From\0Neal P. Murphy <neal.p.murphy@alum.wpi.edu>\0" "Subject\0Re: Reload IPtables\0" "Date\0Mon, 28 Jun 2021 22:02:41 -0400\0" - "To\0\0" + "To\0unlisted-recipients:; (no To-header on input)\0" "Cc\0netfilter-devel@vger.kernel.org" " netfilter@vger.kernel.org\0" "\00:1\0" @@ -30,4 +30,4 @@ "\n" Is iptables-restore truly atomic in *all* cases? Some years ago, I found through experimentation that some rules were 'lost' when restoring more than 25 000 rules. If I placed a COMMIT every 20 000 rules or so, then all rules would be properly loaded. I think COMMITs break atomicity. I tested with 100k to 1M rules. I was comparing the efficiency of iptables-restore with another tool that read from STDIN; the other tool was about 5% more efficient. -3385c16d48eb061982e1acf20ff952e0d9b82795b68c218705a05ff370d49ced +f3c47ad08528a0b864796313b42df244b363c5a07b1e957eff1d43ec0e53b240
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.