>Number: 2710
>Category: config
>Synopsis: configure breaks if you have more than one 'search' entry in
>the resolv.conf.
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Sat Jul 25 02:20:00 PDT 1998
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.3.1
>Environment:
not relevant.
>Description:
configure breaks if you have more than one domain name listed in your
/etc/resolv.conf in a 'search' directive. IMHO, this isnt the right
way to do this at all- what guarantee is there that they have a resolv.conf
and that they have only a single domain name listed in the 'search' statement?
>How-To-Repeat:
in /etc/resolv.conf:
search foo.domain.com
search bar.otherdomain.com
then ./configure normally in the apache source directory
>Fix:
figure out a smarter way of getting the domain name (duh.) perhaps check to see
if
there is more than one domain listed in the /etc/resolv.conf, and if so prompt
the
user for the correct domain name, using the first one found as the default
value.
The configure script looks incredibly broken. example:
domainname="`egrep '^[ ]*search' /etc/resolv.conf |\
sed -e 's/.*search//' -e 's/^[ ]*//' \
-e 's/^ *//' -e 's/^ *//' \
-e 's/ .*//' -e 's/^\.//' -e 's/^/./'`"
ugly!!!! thats the most heinous sed script i've ever seen! it can be reduced to
this:
domainname="`awk '/search/ { print "."$2 }' /etc/resolv.conf`
someone needs to rewrite this configure. its terrible.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
