On Mon, Feb 11, 2002 at 01:11:51PM -0500, Bill Davidsen wrote:
> What is the first thing anyone would do if they had a problem with
> iptables? Turn on debugging, obviously.
yes, I totally agree. I'm not arguing that the current behaviour is OK -
of course it should work with debugging enabled. All I said is that under
normal circumstances a production system is not supposed to have debugging
enabled.
> 2 - it really should work, debug should find errors, not cause them.
of course. That is why debugging does extra checks, which are disabled
in production use. Unfortunately we missed one check...
> 3 - Perhaps debug could be disabled but default, so instead of needing
> NDEBUG in production, you would use -DDEBUG when you had a problem
> (and it might even work ;-).
Yes, this is what I'm doing for the iptables-1.2.6 release. The current
-DNDEBUG stuff has historical reasons which are no longer valid.
> bill davidsen <davidsen@tmr.com>
-- Live long and prosper - Harald Welte / laforge@gnumonks.org http://www.gnumonks.org/ ============================================================================ GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M+ V-- PS++ PE-- Y++ PGP++ t+ 5-- !X !R tv-- b+++ !DI !D G+ e* h--- r++ y+(*) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:00:47 EST