[csw-maintainers] CSWoldap

Sebastian Kayser skayser at opencsw.org
Mon Feb 15 23:56:18 CET 2010

Dagobert Michelsen wrote on 15.02.2010 22:15:
> Am 15.02.2010 um 19:43 schrieb rupert THURNER:
>> On Mon, Feb 15, 2010 at 09:43, Dagobert Michelsen <dam at opencsw.org> wrote:
>>> Am 11.02.2010 um 14:26 schrieb Mantock David:
>>> I made the following packages yesterday and I have now loaded them  
>>> in to build farm NFS share: /home/testing
>>> openldap_client-2.4.19,REV=2010.02.10-SunOS5.8-sparc-CSW.pkg.gz
>>> openldap_devel-2.4.19,REV=2010.02.10-SunOS5.8-sparc-CSW.pkg.gz
>>> openldap_rt-2.4.19,REV=2010.02.10-SunOS5.8-sparc-CSW.pkg.gz
>>> openldap-2.4.19,REV=2010.02.10-SunOS5.8-sparc-CSW.pkg.gz
>>> They are available for testing on http://mirror.opencsw.org/opencsw/testing
>>> Apart from making x86 versions is there something else I should do?
>>> The following things need to be either verified or implemented in  
>>> the package:
>>> - Check that the package works (start server, stop server on  
>>> Solaris 8/9 RC and 10 SMF)
>>> - Check functionality (create database, populate, access via SSL  
>>> and Kerberos)
>>> - Check upgrade path from existing OpenLDAP package (especially  
>>> relocation of database
>>>  from /opt/csw/var to /var/opt/csw), conversion of database from  
>>> BDB 4.4 to 4.7.
>>>  If the upgrade is not straight-forward it needs to be documents.
>> how can we avoid the database move to /var/opt ?
> Well, IIRC we wanted to move all writable data to /var/opt/csw to be  
> more sparse-zone friendly for r/o shared /opt. The moving itself is
> with cswmigrateconf no big deal. Or do you have other reasons in mind
> to not move it?

Rupert once posted details about the particular setup at his workplace
and the constraints that come along with it [1]. I think it was the
requirement to have everything under /opt/csw that they were after, I
don't know whether that still holds true though. Rupert?



More information about the maintainers mailing list