directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bastiaan Bakker (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-749) fix issues with apacheds RPM to get it working out of the box
Date Mon, 25 Sep 2006 09:23:51 GMT
    [ http://issues.apache.org/jira/browse/DIRSERVER-749?page=comments#action_12437491 ] 
            
Bastiaan Bakker commented on DIRSERVER-749:
-------------------------------------------

"* JAVA_HOME: ... We need it to compile the schema classes if you modify the schema. Alex
will confirm that, I think. "

I see. I thought all schema classes needed to be precompiled? In any case if a compiler isn't
needed now, it will be in the future. If we should depend on the JDKs compiler or use another
one (like Tomcat does) is a question for another time.

* Running non root: the patch uses username 'apacheds', but it's configurable in the POM.
I'd rather avoid 'ldap' because at least on Fedora that one is already used by OpenLDAP. The
RPM usess 'useradd -r' to create a system account, but I see that still gives it a valid shell.
I'll create a separte patch to fix that. chroot would be nice but I would want to do that
for a default setup because it complicates it a lot (need to replicate all JVM stuff etc.
inside the chroot). 

* using ApacheDS in production. Currently we're using ApacheDS to connect FreeRADIUS to an
internal Oracle user account DB via LDAP. For that we wrote a simple Partition implementation
that looks up entries through JDBC. We have another ApacheDS backend in development for replication
of LDAP trees to other database: it publishes LDAP updates to a JMS topic where they can be
read by database specific update jobs.
We also plan to use ApacheDS as a rewriting LDAP proxy. 
So, we don't store any entries in ApacheDS yet, we still use OpenLDAP for that. But maybe
that we'll change once ApacheDS has proven itself.

Cheers
 




> fix issues with apacheds RPM to get it working out of the box
> -------------------------------------------------------------
>
>                 Key: DIRSERVER-749
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-749
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: installer-plugin
>    Affects Versions: 1.0-RC4
>         Environment: linux
>            Reporter: Bastiaan Bakker
>         Attachments: apacheds-branch-1.0-server-installers-rpmfix.patch, apacheds-daemon-trunk-rpmfix.patch
>
>
> The apacheds RPM has several issues that prevent it from running out of the box:
> * the init script fails to run because APACHEDS_USER is set to $USER, which is not defined
at boot time
> * the init script fails to run bevause JAVA_HOME is not defined
> * the init script it is not registered to the init subsystem with chkconfig or similar
> * the config files are not marked as such, causing them to be silently overwritten when
one upgrades the RPM
> * the RPM filename is not conform conventions: ${name}-${version}-${release}.${arch}.rpm
> * the location of the files (/usr/local/apacheds-1.0_RC4) is version dependent, making
upgrades cumbsome. The admin has to relocate the partitions and config files on every updgrade.
> * the sources and docs are included in the rpm, even though they are not necessary for
operation.
> The RPM build mechanism for apacheds also has some issues:
> * runs rpmbuild as root, which is frowned upon by RPM gurus for security and safety reasons.
> * the generated src.rpm is not self contained, ie. one cannot do a 'rpmbuild --rebuild'
with it. 
> * the sudo mechanism is totally unnecessary
>  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message