directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Karasulu <akaras...@apache.org>
Subject Re: [ApacheDS 2.0] Installation layout
Date Fri, 17 Sep 2010 03:19:49 GMT
Excellent! Thanks,
Alex

On Thu, Sep 16, 2010 at 10:38 AM, Pierre-Arnaud Marcelot <pa@marcelot.net>wrote:

> As I'm reviewing these layout, I'm also reviewing the installers.
>
> I'm happy to tell you that I've recompiled the Tanuki Service Wrapper 3.2.3
> sources (the one with the correct license for our use) with 64bit support
> and I built the wrapper as a Mac OS X Universal 64bit library.
>
> This will avoid a nasty warning when launching the wrapper on Snow Leopard
> which is bundled with a 64bit JVM.
>
> We will no longer see this message in the wrapper logs:
> > STATUS | wrapper  | 2010/09/15 19:03:55 | Launching a JVM...
> > INFO   | jvm 1    | 2010/09/15 19:03:55 | Initializing...
> > INFO   | jvm 1    | 2010/09/15 19:03:56 | Wrapper (Version 3.2.3)
> http://wrapper.tanukisoftware.org
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |   Copyright 1999-2006 Tanuki
> Software, Inc.  All Rights Reserved.
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |
> > INFO   | jvm 1    | 2010/09/15 19:03:56 | WARNING - Unable to load the
> Wrapper's native library 'libwrapper.jnilib'.
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |           The file is located
> on the path at the following location but
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |           could not be loaded:
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |
> /Users/pajbam/Desktop/ApacheDSTesting/bin/../lib/libwrapper.jnilib
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |           Please verify that
> the file is readable by the current user
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |           and that the file has
> not been corrupted in any way.
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |           One common cause of
> this problem is running a 32-bit version
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |           of the Wrapper with a
> 64-bit version of Java, or vica versa.
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |           This is a 64-bit JVM.
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |           Reported cause:
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |
> /Users/pajbam/Desktop/ApacheDSTesting/lib/libwrapper.jnilib:  no suitable
> image found.  Did find:
>  /Users/pajbam/Desktop/ApacheDSTesting/lib/libwrapper.jnilib: no matching
> architecture in universal wrapper
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |           System signals will
> not be handled correctly.
> > INFO   | jvm 1    | 2010/09/15 19:03:56 |
>
>
> I will include the new wrapper files in the branch later today.
>
> Cheers,
> Pierre-Arnaud
>
>
> On 15 sept. 2010, at 10:26, Pierre-Arnaud Marcelot wrote:
>
> > I created two branches to work on those refactorings:
> > -
> https://svn.apache.org/repos/asf/directory/daemon/branches/daemon-apacheds-2.0
> > -
> https://svn.apache.org/repos/asf/directory/installers/branches/installers-apacheds-2.0
> >
> > Regards,
> > Pierre-Arnaud
> >
> >
> > On 14 sept. 2010, at 18:47, Kiran Ayyagari wrote:
> >
> >> On Tue, Sep 14, 2010 at 9:14 PM, Pierre-Arnaud Marcelot <
> pa@marcelot.net> wrote:
> >>> Hi Dev,
> >>>
> >>> Since the 'server.xml' is now dead and buried, and the 2.0 release
> approaching, I'd like to start the refactoring of the installers and
> installation layouts.
> >>>
> >>> ApacheDS 1.5.x supported multiple instances (with a default instance
> created with each native installer), I think Apache DS 2.0 should continue
> to support this feature.
> >>> In order to do that, two default layouts need to be (re-)defined, one
> for Apache DS itself (the InstallationLayout) and one for each instance (the
> InstanceLayout).
> >>>
> >>> InstallationLayout
> >>> ------------------------
> >>> /bin
> >>> /bin/apacheds(.exe)                     --> ApacheDS (Tanuki) wrapper
> >>> /bin/apacheds-tools(.bat)               --> ApacheDS Tools command line
> script
> >>> /conf/wrapper.conf                      --> Tanuki Wrapper
> configuration (common to all instances)
> >>> /lib/                                                   --> Folder for
> all ApacheDS libraries
> >>> /lib/lib-a.jar
> >>> [...]
> >>> /lib/lib-z.jar
> >>>
> >>> InstanceLayout
> >>> ---------------------
> >>> /conf/
> >>> /conf/wrapper.conf                      --> Tanuki Wrapper
> configuration (specific to this instance)
> >>> /conf/log4.properties                   --> Log4J configuration
> >>> /conf/config.ldif                               --> LDIF based
> configuration file (also accessible under 'ou=config' when the server is
> started)
> >>> /log/
> >>> /log/apacheds-rolling.log               --> Log file (could also be
> placed at /var/log/apacheds-instancename/ under linux)
> >>> /partitions/                                    --> Folder for all
> partition (except 'config')
> >>> /partitions/example                     --> Example partition folder
> >>> /partitions/schema                      --> Schema partition folder
> >>> /partition/system                               --> System partition
> folder
> >>> /run/
> >>> /run/apacheds.pid                       --> Apache DS instance pid file
> when the server is running (could also be placed at /var/run/... under
> linux)
> >>>
> >>> Here's the layouts I had in mind.
> >>> I tried to keep most of the existing stuff we already had.
> >>>
> >>> There are some things which need an extra work (like the LDIF based
> configuration on a single file, as well as the ability to save that outside
> of the boundaries of the 'partitions' folder.
> >>> But I really think having all configuration files stored in a single
> location is a must.
> >> +1 it makes a lot of sense to have all config files at one location
> >>
> >>
> >> Kiran Ayyagari
> >
>
>


-- 
Alex Karasulu
My Blog :: http://www.jroller.com/akarasulu/
Apache Directory Server :: http://directory.apache.org
Apache MINA :: http://mina.apache.org
To set up a meeting with me: http://tungle.me/AlexKarasulu

Mime
View raw message