[
https://issues.apache.org/jira/browse/SOLR-7826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681977#comment-14681977
]
Shawn Heisey commented on SOLR-7826:
------------------------------------
bq. Perhaps bin/solr always should bail out early if executed as root, perhaps
with an --runasrootonyourownrisk param to override?
Sounds awesome to me. There's another project that does something similar to
protect the user from themselves, and the option to explicitly force the action
is not documented anywhere except in the program output, which I think is a
reasonable thing to do here.
I want to say that it's the linux raid tools (mdadm) that has the undocumented
"I really know what I'm doing, please proceed" option, but I can no longer
remember ... and google isn't helpful since it's not documented. ;)
> Permission issues when creating cores with bin/solr
> ---------------------------------------------------
>
> Key: SOLR-7826
> URL: https://issues.apache.org/jira/browse/SOLR-7826
> Project: Solr
> Issue Type: Improvement
> Reporter: Shawn Heisey
> Priority: Minor
>
> Ran into an interesting situation on IRC today.
> Solr has been installed as a service using the shell script
> install_solr_service.sh ... so it is running as an unprivileged user.
> User is running "bin/solr create" as root. This causes permission problems,
> because the script creates the core's instanceDir with root ownership, then
> when Solr is instructed to actually create the core, it cannot create the
> dataDir.
> Enhancement idea: When the install script is used, leave breadcrumbs
> somewhere so that the "create core" section of the main script can find it
> and su to the user specified during install.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
