[ http://issues.apache.org/jira/brows...243
6884 ]

Bastiaan Bakker commented on DIRSERVER-749:
-------------------------------------------

Thanks for the positive feedback.
Some comments on your comments :-)

* JAVA_HOME: Currently I've set it to /usr/lib/jvm/java, because that is the
 location for the default Java installation with JPackages alternatives syst
em. This is also used by Fedora and RHEL and any other distro using JPackage
. I would like to set it to
/usr/lib/jvm/jre, because then you would only need the JRE and not the JDK t
o run apacheds. But the init script puts $JAVA_HOME/lib/tools.jar in CLASSPA
TH, which only works when using the JDK. Does any part of the apacheds serve
r actually need tools.jar?


* location. Maybe RCs are not supposed to be used in production, but in real
ity they are (at least in our datacenter). In any case I would prefer to to 
have the RCs look like production version as much as possible (the y aren't 
called Release Candidated f
or nothing)

*  running non-root: which user to run as is configurable at rpm build time 
in pom.xml and at runtime in /etc/sysconfig/apacheds. The current server.xml
 listens on port 10389 so running non root isn't a problem with the default 
config. In cases where I ne
ed it to listen to port 389 I prefer to run it non-root with a high port and
 create an iptables rule to forward 389 to the high port.

* sources and help: with RPM you don't launch an installer so that wouldn't 
be an option. But I've put them in two subpackages so users can choose wheth
er to install sources and docs or not.

On my todo / wish list:
* run Java in server mode
* add status command to initscript
* restart apacheds after upgrade
* Filesystem Hierarchy Standard compliance
* logging to syslog by default
* fix the bogus installation check warning
* create a proper src.rpm which rebuilds apacheds from source
* inclusion in JPackage



> 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, a
pacheds-daemon-trunk-rpmfix.patch
>
>
> The apacheds RPM has several issues that prevent it from running out of th
e box:
> * the init script fails to run because APACHEDS_USER is set to $USER, whic
h 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 chkconfi
g or similar
> * the config files are not marked as such, causing them to be silently ove
rwritten 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 depen
dent, 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 n
ecessary 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 a
nd safety reasons.
> * the generated src.rpm is not self contained, ie. one cannot do a 'rpmbui
ld --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://iss
ues.apache.org/ji...nistrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]