[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: BDB Corruption...

On Wed, 2004-10-20 at 11:12, Dominic Ijichi wrote:
> Quoting Tony Earnshaw <tonye@billy.demon.nl>:
> > ons, 20.10.2004 kl. 04.42 skrev Quanah Gibson-Mount:
> > 
> > >
> > > I simply suggest not using RedHat. :)
> > 
> > I have many reasons for sticking with RH; it's just the whole attitude
> > to directory services (and RDBs for that matter) that gets my goat.
> > 
> > AFAIK the only OS that officially offers Openldap 2.2 as a standard
> > update, is FreeBSD; for all the others one has to jump through hoops. I
> > can understand that the jump from 2.0 to 2.2 could break client
> > applications, but surely the user should be given the choice and offered
> > the assistance in adopting modern technology, especially when the
> > software authors urge doing so? And I don't regard offering Netscape
> > Directory Server as being the answer ...
> after having exclusively used heavily hacked/customised redhat for years and
> years, i switched this year to suse.  Suse Linux Enterprise Server 9 has
> OpenLdap2.2 as standard, more than that it uses it as the standard backend for
> users, groups AND a lot of the system configuration.  I have a 2-server cluster
> with near-realtime journalled replication, a decent FS (Reiser!), failover
> host/service/network clustering, and DHCP, DDNS, Samba PDC, SMTP/IMAP, HTTP all
> using a openldap backend for auth/config.  This is without a single line of
> custom/compiled code or config, all configured through a GUI (well, a couple of
> lines of cluster stuff by hand).
> redhat for me is consigned to the bin forever, Novell/Suse rocks.
> ------------------------------------------
> This message was penned by the hand of Dom

I have used OpenLDAP 2.2.6 on SuSE as well, and was very pleased with
the deployment and architecture the RPM provided.  However, I quickly
ran into some sort of weird bug that caused it to crash whenever I
pointed phpLDAPAdmin at it.  I ended up "rolling my own" heavily
customized OpenLDAP 2.2.15 RPM.

I agree with the oft given advice on the list:  it is often better to
avoid the distro's packaged OpenLDAP, and compile your own.  However, I
would *strongly* recommend using /some/ package method (RPM, APT, Stow,
even ./configure --prefix=/some/isolated/location) when you compile your
own -- this will ease the upgrade pain, and make future deployments
easier.  Plus, if your distro of choice does ever package a 'modern'
version (any distro packaging 2.2.17 yet??), it will be simpler to
migrate if you so choose.

Good luck to all you custom-rollers out there!

Matthew J. Smith <matt.smith@uconn.edu>
University of Connecticut ITS
PGP Key: http://web.uconn.edu/dotmatt/matt.asc