[
https://issues.apache.org/jira/browse/SOLR-9325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-9325:
------------------------------
Attachment: SOLR-9325.patch
First patch. Sets {{-Dsolr.log.dir=$SOLR_LOGS_DIR}} in start script and uses
variable $\{solr.log.dir\} in log4j.properties. Default still set to relative
"logs".
NOT tested at all on Windows (anyone?), tested some on macOS
> solr.log written to {solrRoot}/server/logs instead of location specified by
> SOLR_LOGS_DIR
> -----------------------------------------------------------------------------------------
>
> Key: SOLR-9325
> URL: https://issues.apache.org/jira/browse/SOLR-9325
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 5.5.2, 6.0.1
> Environment: 64-bit CentOS 7 with latest patches, JVM 1.8.0.92
> Reporter: Tim Parker
> Attachments: SOLR-9325.patch
>
>
> (6.1 is probably also affected, but we've been blocked by SOLR-9231)
> solr.log should be written to the directory specified by the SOLR_LOGS_DIR
> environment variable, but instead it's written to {solrRoot}/server/logs.
> This results in requiring that solr is installed on a writable device, which
> leads to two problems:
> 1) solr installation can't live on a shared device (single copy shared by two
> or more VMs)
> 2) solr installation is more difficult to lock down
> Solr should be able to run without error in this test scenario:
> burn the Solr directory tree onto a CD-ROM
> Mount this CD as /solr
> run Solr from there (with appropriate environment variables set, of course)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
