[
https://issues.apache.org/jira/browse/JENA-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061824#comment-15061824
]
Andy Seaborne edited comment on JENA-1099 at 12/17/15 10:05 AM:
----------------------------------------------------------------
The commit above implements option 1 which provides the most compatibility with
the existing releases. It also means that default behaviour is not to require
being a user with access to /etc/fuseki. Option 3 gets quite complicated.
was (Author: andy.seaborne):
The commit above implement option 1 which provides the most compatibility with
the existing releases. It also means that default behaviour is not to require
being a user with access to /etc/fuseki. Option 3 gets quite complicated.
> 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)
