[
https://issues.apache.org/jira/browse/JENA-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1099.
---------------------------------
Resolution: Fixed
Assignee: Andy Seaborne
Fix Version/s: Fuseki 2.4.0
The commits are the most compatible approach and at least make
{{/etc/default/fuseki}} as people expect.
If there is a contribution, with documentation, to make the default
{{/etc/defaul/fuseki}}, with existing deployment support, that would be
interesting. It would be good to survey the users as to which they prefer. ACL
issues with system files need to be addressed.
> 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
> Assignee: Andy Seaborne
> Fix For: Fuseki 2.4.0
>
>
> 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)
