[
https://issues.apache.org/jira/browse/JENA-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Pritts resolved JENA-1217.
------------------------------
Resolution: Fixed
Fix Version/s: Fuseki 2.4.0
Looks like it. Sorry for the dupe.
> fuseki init script problems - FUSEKI_BASE doesn't work - other env var won't
> either
> -----------------------------------------------------------------------------------
>
> Key: JENA-1217
> URL: https://issues.apache.org/jira/browse/JENA-1217
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 2.3.1
> Environment: RHEL 6.x
> Reporter: Dan Pritts
> Priority: Minor
> Fix For: Fuseki 2.4.0
>
>
> Ran into several problems with the fuseki init script, filing multiple bugs,
> but if you are working on one you might consider addressing them all. Hope
> this is the right approach.
> The docs and comments in /etc/default/fuseki say that FUSEKI_BASE can be set
> in /etc/default/fuseki.
> However, setting it there has no effect, it still uses .../run.
> I traced this problem down to the fact that the FUSEKI_BASE environment
> variable is neither `export`ed from the shell script, nor specified as a `-D`
> on the java command line. Alternately, you could add support for changing
> this on the fuseki command line by adding, perhaps, a --base option.
> using -D is kind of ugly. I would prefer the export option. Perhaps best
> would be adding a command line option, and setting that option from the init
> script as appropriate.
> If you do the export, I suggest adding it right after you source the config
> file.
> I'm not sure what other environment variables Fuseki might read, but they
> will all need to be passed down somehow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
