I'm playing with Fuseki 2.3.1 on Centos 7.2, which is based on systemd. Despite that, the "fuseki" init script should work.
FUSEKI_HOME and FUSEKI_BASE are set explicitly in /etc/defaults/fuseki. (/opt/fuseki is a symlink to /opt/apache-jena-fuseki-2.3.1) The DEBUG output of the script reports: FUSEKI_HOME = /opt/fuseki FUSEKI_BASE = /etc/fuseki FUSEKI_CONF = FUSEKI_RUN = /var/run FUSEKI_PID = /var/run/fuseki.pid FUSEKI_ARGS = FUSEKI_START = /opt/fuseki/fuseki-server.jar FUSEKI_CLASSES = CONFIGS = However, /etc/fuseki/logs/stderrout.log shows: [2015-12-16 12:50:13] Server INFO Fuseki 2.3.1 2015-12-08T09:24:07+0000 [2015-12-16 12:50:13] Config INFO FUSEKI_HOME=/opt/apache-jena-fuseki-2.3.1/. [2015-12-16 12:50:13] Config INFO FUSEKI_BASE=/opt/apache-jena-fuseki-2.3.1/run Now - when I set export FUSEKI_HOME=/opt/fuseki export FUSEKI_BASE=/etc/fuseki in my interactive bash shell, and invoke the init script again, fuseki is loaded correctly, including the services in /etc/fuseki/configuration. Not sure if this is related to systemd, or if I missed something completely unrelated - did anybody else see similar errors? Cheers, Joachim
