httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Querna <>
Subject [PATCH] mod_unique_id: Keep running w/ Broken DNS
Date Wed, 16 Jun 2004 02:12:35 GMT
In #apache on FreeNode IRC, mod_unique_id is one of the most common
problems.  Thanks to some distributions (ahem. gentoo.), that commonly
do not configure DNS correctly, and enable mod_unique_id by default,
several times a day people come in saying apache will not start for

I see three ways to solve this issue:
1) Make the error we spit out more verbose when DNS is broken.
2) Continue running, turning off mod_unique_id.
3) Complain to upstream vendors.(don't enable mod_unique_id by default!)

Most of the people with this problem have no reason to be running
mod_unique_id, but their distro has enabled it, so I believe the best
method is to spit out info about it in the error log, but to keep Apache

The attached patch is a quick hack to let mod_unique_id disable itself
if the DNS resolution fails.  

No matter what is done, It would be nice to have some sort of change
into 2.0.50 before a release is made.


-Paul Querna

View raw message