Bug#445298: When packaging new version
When packaging the new version, please note the difference in the README about performance notes, specifically: 2. Make sure to build dkim-filter using the asynchronous (ARLIB) resolver. This is accomplished by modifying site.config.m4 to enable these lines: define(`bld_USE_ARLIB', `True') Micah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445298: When packaging new version
On Thu, Oct 04, 2007 at 03:05:14PM -0400, Micah Anderson [EMAIL PROTECTED] wrote: When packaging the new version, please note the difference in the README about performance notes, specifically: 2. Make sure to build dkim-filter using the asynchronous (ARLIB) resolver. This is accomplished by modifying site.config.m4 to enable these lines: define(`bld_USE_ARLIB', `True') I'm well aware of arlib and waiting to see the current revision in wider production use before enabling it in the package. -- Mike Markley [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445298: When packaging new version
* Mike Markley [EMAIL PROTECTED] [071004 14:49]: On Thu, Oct 04, 2007 at 03:05:14PM -0400, Micah Anderson [EMAIL PROTECTED] wrote: When packaging the new version, please note the difference in the README about performance notes, specifically: 2. Make sure to build dkim-filter using the asynchronous (ARLIB) resolver. This is accomplished by modifying site.config.m4 to enable these lines: define(`bld_USE_ARLIB', `True') I'm well aware of arlib and waiting to see the current revision in wider production use before enabling it in the package. It seems that the two critical issues are that the standard bind resolver doesn't provide the DK information properly when a CNAME is involved and arlib's asynchronous library can handle significantly more requests. The first one seems more critical, the latter being more performance related. Micah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
