[
https://issues.apache.org/jira/browse/SOLR-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008876#comment-16008876
]
Jan Høydahl commented on SOLR-7505:
-----------------------------------
I think this is fixed, the linux installer by default makes /opt/solr read-only
to solr user and that's ok as long as you don't try to use that location for
solr-home, pid or logs
> startup scripts - read-only install dir and other improvements
> --------------------------------------------------------------
>
> Key: SOLR-7505
> URL: https://issues.apache.org/jira/browse/SOLR-7505
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Affects Versions: 5.1
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Minor
>
> Talking to a user on IRC, I've come across some things we could do better in
> our startup scripts and the documentation around them.
> * It's very difficult to make the entire install directory read-only from
> the point of view of the RUNAS user.
> ** The war must be extracted, by default this is done to server/solr-webapp.
> ** Fixing this will require a few changes to the scripts as well as some
> additions to the documentation. I'm not suggesting that we make this a
> default setup, just provide information on how a user can accomplish it.
> * If SOLR_ENV is pointed at a script that is empty, nonexistent, or only
> includes minimal user settings, the settings for default max heap and GC
> tuning are lost, and return to undesirable Java defaults. I believe that a
> user env file should *supplement* solr.in.{sh,cmd}, not *replace* it. The
> user can always completely override the provided defaults in their env file.
> There were some other ideas I had, will update if I remember them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
