The first line in /etc/conf.d/hsqldb is "JAVA_EXECUTABLE=$(java-config --java)". This can lead to an error message during boot because the config-file is being evaluated before any mounts. In case you have /usr on a seperate partition, you'll get this error message: "java-config not found".
I think this should be able to be fixed by making the init.d depend on the localmount init.d, which in turn mounts the local filesystems.
But why should this be dynamic? /usr/bin/java is a symlink anyway, isn't it?
(In reply to comment #1) > I think this should be able to be fixed by making the init.d depend on the > localmount init.d, which in turn mounts the local filesystems. > I think localmount is in "boot" runlevel and this belongs to "default" so that's not issue. The problem would be (if it's true, which would seem odd to me) that the script's conf.d files are evaluated beforehand, and not when the script is really executed.
Revision was bumped to take advantage of new Java system. This should address this issue as well. Thanks for reporting.
(In reply to comment #4) > Revision was bumped to take advantage of new Java system. This should address > this issue as well. Thanks for reporting. > Still exists with dev-db/hsqldb-1.7.3.1-r3
hit the wrong radio button
Should be fixed in 1.8.0.9 which sets JAVA_EXECUTABLE=/usr/bin/java