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

Re: Update strategy: 2.3.34 to 2.3.41 or even 2.4.9 ?

To: OpenLDAP Software List <openldap-software@openldap.org>
Subject: Re: Update strategy: 2.3.34 to 2.3.41 or even 2.4.9 ?
From: Dave Horsfall <daveh@coreng.com.au>
Date: Thu, 22 May 2008 08:31:54 +1000 (EST)
Archive: No
Content-id: <20080522083105.B80285@mippet.ci.com.au>
In-reply-to: <4833D424.7070905@stroeder.com>
References: <20080518160538.bjoqvjxmc0s8wsos@login-13.hoststar.ch> <20080521083931.L36967@mippet.ci.com.au> <4833D424.7070905@stroeder.com>

On Wed, 21 May 2008, Michael Ströder wrote:

> At the moment I'd only consider migrating to 2.4.x for production if new 
> features are needed. Some tweaking of slapd.conf might be required 
> during migration.

Agreed; we run 2.4 clients because of a timeout that we needed, but the 
servers are still 2.3.  The installation method is...interesting...

-- 
Dave Horsfall DTM VK2KFU  Ph: +61 2 9552-5509 (direct) +61 2 9552-5500 (switch)
Corinthian Eng'ng P/L, Ste 54 Jones Bay Whf, 26-32 Pirrama Rd, Pyrmont 2009, AU

Follow-Ups:
- Re: Update strategy: 2.3.34 to 2.3.41 or even 2.4.9 ?
  - From: Gavin Henry <ghenry@OpenLDAP.org>

References:
- Update strategy: 2.3.34 to 2.3.41 or even 2.4.9 ?
  - From: openldap.lists@frei-family.ch
- Re: Update strategy: 2.3.34 to 2.3.41 or even 2.4.9 ?
  - From: Dave Horsfall <daveh@coreng.com.au>
- Re: Update strategy: 2.3.34 to 2.3.41 or even 2.4.9 ?
  - From: Michael Ströder <michael@stroeder.com>

Prev by Date: suffixmassaging to ancestor suffix
Next by Date: Unexpected crash
Index(es):
- Chronological
- Thread