directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-749) fix issues with apacheds RPM to get it working out of the box
Date Fri, 22 Sep 2006 16:20:16 GMT
    [ http://issues.apache.org/jira/browse/DIRSERVER-749?page=comments#action_12436893 ] 
            
Emmanuel Lecharny commented on DIRSERVER-749:
---------------------------------------------

"* JAVA_HOME: ... Does any part of the apacheds server actually need tools.jar? "

Well, hmmm, yes. We need it to compile the schema classes if you modify the schema. Alex will
confirm that, I think.

* RC & Location : ok, I understand your concern. I don't think we will have a lot of RCx
after RC4, so this concern will vanish in a near futur. So you are using it in production?
That's quite a good news. We will really appreciate any feedback about it - pbs, of course,
but also usage statistic, number of entries, and of course a testimonywe will add to the site
:)

* Running non-root : I didn't get it the first time. You are perfectly right. I think the
best approach would be to use a port which is not 389, and use a special account like 'ldap',
with a /bin/null as shell, and into a chrooted space.

* Sources : Sorry, again, I have made the bad assumption you were using the .jar, which is
an installer. 

We will try to apply your patch asap;

Thanks !!!

> 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