Bug 27612 - DNS support needed
DNS support needed
Status: CLOSED RAWHIDE
Product: Red Hat Powertools
Classification: Retired
Component: webalizer (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Powers
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-14 08:50 EST by Jean-Luc Fontaine
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-14 11:16:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Jean-Luc Fontaine 2001-02-14 08:50:38 EST
NOTE: this is for fisher powertools.

Does not allow reverse name lookups, a very important new feature of 2.01.
For example:

$ webalizer -D dns.db -N 10
does nothing more.

and after symbolically linking webalizer to:
$ webazolver 
DNS support not present, aborting...

It should be trivial to fix in the spec file.
Other than that Redhat 7.1b seems to work just fine. Thanks!

Regards, Jean-Luc
Comment 1 Tim Powers 2001-02-14 11:16:10 EST
Fixing the product/component.
Comment 2 Tim Powers 2001-02-14 12:27:08 EST
It took some digging, but it was sucking in the wrong header for db, it needed
<db1/db.h> instead of <db.h> (which is db3). This is why when configuring wiht
the --with-dns option and then building would fail in the past (it's expecting
db1 to be the default). In any case, it's fixed, and has dns enabled. I have put
the fixed package in http://people.redhat.com/timp/RPMS/webalizer-2.01_06-5.i386.rpm
and the SRPM in http://people.redhat.com/timp/SRPMS/webalizer-2.01_06-5.src.rpm .

These packages should also show up in rawhide the next time it's updated.

Tim
Comment 3 Jean-Luc Fontaine 2001-02-14 12:47:32 EST
I tested it and it works.
Thanks for such a prompt fix! That is what I call efficiency.
Best regards, Jean-Luc.

Note You need to log in before you can comment on or make changes to this bug.