[
https://issues.apache.org/jira/browse/JENA-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061802#comment-15061802
]
ASF subversion and git services commented on JENA-1099:
-------------------------------------------------------
Commit 9ab8584002c59fcac6e917463f42ec96ade73ab5 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=9ab8584 ]
JENA-1099: Export FUSEKI_HOME and FUSEKI_BASE
Default FUSEKI_BASE to $FUSEKI_HOME/run
It was not being exported. This is the compatible setting
as it agrees with the java setup.
Remove FUSEKI_DATA_DIR
Wrong value (was $FUSEKI_HOME/DB)
Not used for anything
Don't create $FUSEKI_DATA_DIR
Remove DATA_DIR (not used)
> Fuseki service script does not export FUSEKI_HOME and FUSEKI_BASE
> -----------------------------------------------------------------
>
> Key: JENA-1099
> URL: https://issues.apache.org/jira/browse/JENA-1099
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 2.3.0
> Reporter: Andy Seaborne
>
> The usual style with {{/etc/defaults/...}} is to set but not export
> variables, leaving it to the calling script to manage environment variables.
> The "fuseki" script does not export FUSEKI_HOME and FUSEKI_BASE so the
> settings do not progate to the exec'ed java process.
> The script and the java default happen to be the same which hides the issue
> much of the time. The service script should always export these two variables.
> Workaround:
> In {{/etc/default/fuseki}}, export FUSEKI_HOME and FUSEKI_BASE, not just set
> them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
