Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 4523 - SWS 2.0 on RH 6.0 incompatible berkeley DB
SWS 2.0 on RH 6.0 incompatible berkeley DB
Product: Red Hat Secure Web Server
Classification: Retired
Component: secureweb (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Preston Brown
Depends On:
  Show dependency treegraph
Reported: 1999-08-14 18:06 EDT by adi
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-13 10:36:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description adi 1999-08-14 18:06:29 EDT
RH 6.0 ships with Berkeley DB 2.1.1.

SWS 2.0 needs Berkeley DB 1.85 for AuthDBUserFile and

I could not get SWS 2.0 to read my db files no matter which
interface I used (/usr/include/db1/db.h,
/usr/include/db_185.h, etc)  The only solution was to
compile and install the original Berkeley DB 1.85

However, that was easier said than done, since I believe
there was an incompatibility in egcs with the 1.85 source.
I'm not sure exactly what package caused the conflict, but I
patched it.  See the patch for details.

Everything works now with my new SRPM,  see the URL above.
Once you install it, you need to rebuild the perl DB_File
module (or whatever you're using to maintain AuthDB*Files)
with the new /usr/lib/libdb-1.85.so and
Comment 1 Preston Brown 1999-08-23 11:17:59 EDT
Jeff, these db problems have been sorted out for 6.1 already, correct
or incorrect?
Comment 2 Preston Brown 2000-01-13 10:36:59 EST
please upgrade to Secure Web Server 3.1 -- you can get it for free.  Please
contact sales regarding this -- you will have to return your Secure Web Server
2.0 CDs.

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