[ http://issues.apache.org/jira/brows...ER-749?page=all ]

Bastiaan Bakker updated DIRSERVER-749:
--------------------------------------

Attachment: apacheds-daemon-trunk-rpmfix.patch
apacheds-branch-1.0-server-installers-rpmfix.patch

The attached patchs are diffs against directory/trunks/daemon/ and directory
/branches/apacheds/1.0 respectively. The provide the following fixes:
* added /etc/sysconfig/apacheds containing JAVA_HOME and APACHEDS_USER
* fix init scripts to set APACHEDS_USER to 'root' if not defined in /etc/sys
config/apacheds
* marked all config files as such
* build RPM as regular user using 'rpmbuild --define "_topdir <dir>"'
* removed no longer needed option <doSudo>
* split sources and docs in subpackages
* add tag <installBase> to <rpmtarget> to specify were apacheds should be in
stalled
* set <installBase> to '/opt/apacheds' so the location doesn't contain a ver
sion number anymore
* add tag <daemonUser> to have apacheds run as a non-root user for security 
reasons
* set <daemonUser> to 'apacheds'
* let RPM create daemonUser upon first install
* let $installBase/var  subdirs be owned by daemonUser
* register initscript with install_initd
* stop daemon before deinstalling RPM
* start apacheds in runlevel 3,4,5


> 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 ]