|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
|
|
Environment:
|
linux
|
|
| Resolution Date: |
09/Aug/07 06:52 AM
|
|
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
|
|
Description
|
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
|
Show » |
| No work has yet been logged on this issue.
|
|
Improvement
Closed
Minor
fix issues with apacheds RPM to get it working out of the box
