[
https://issues.apache.org/jira/browse/SOLR-12777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619203#comment-16619203
]
Shawn Heisey commented on SOLR-12777:
-------------------------------------
The service installer already changes the ownership of server/logs in the
installation directory to the user that is used for the service, even though
the logs do not go there when the service is started. The rest of the install
directory is owned by root. The "var dir" and all its contents are owned by
the service user.
The pidfile ends up in the "var dir" with the service installer, which defaults
to /var/solr if not changed.
When Solr is started without installing it, chances are good that all the files
will be owned by the user that starts it, but this is completely outside our
ability to control.
> Add bin/solr args for specifying PID and LOGS dirs
> --------------------------------------------------
>
> Key: SOLR-12777
> URL: https://issues.apache.org/jira/browse/SOLR-12777
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Affects Versions: 7.3.1
> Reporter: Pete Ryland
> Priority: Major
>
> When starting solr, an optional {{-d}} parameter can be provided. This
> specifies the "Solr server directory" which needs to be the {{server}}
> directory from the raw distribution. This clearly contains the program
> files, so as per common practice should not be writable by the user running
> the program. However, when specified, an error results because it tries to
> create a log directory within the program directory! This is really really
> bad practice. One should be able to specify a directory for the runtime
> files and log files on the command line. It would be even better if the
> defaults conformed to the filesystem hierarchy standard when run on a Linux
> system. I understand that you want to make it easy for developers to use
> your software, but when deploying on actual production systems, these things
> are really important. It's also important to understand that the people
> deploying your software to production are different to the ones who develop
> with your software, and a deep understanding of your software shouldn't be
> necessary for the former to be able to deploy it.
> A wholly-unsatisfactory workaround is to set the pid and log directories by
> environment variable before starting the server:
> {{$ export SOLR_PID_DIR=/var/lib/celum-search}}
> {{$ export SOLR_LOGS_DIR=/var/log/celum-search}}
> This can also be done in {{/etc/default/solr.in.sh}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
