[
https://issues.apache.org/jira/browse/COUCHDB-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362332#comment-14362332
]
Alexander Shorin commented on COUCHDB-2638:
-------------------------------------------
Setting correct permissions for the config files is a part of installation
process. Once it done right, there shouldn't be any permission deny issues.
And /var/db or somewhere else isn't a place where configuration files could be
ever searched for since /etc and /usr/local/etc is the traditional place for
them.
> CouchDB should not be writing /etc/couchdb/local.ini
> ----------------------------------------------------
>
> Key: COUCHDB-2638
> URL: https://issues.apache.org/jira/browse/COUCHDB-2638
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Yuri
>
> I am getting such messages in log on FreeBSD:
> > Could not write config file /usr/local/etc/couchdb/local.ini: permission
> > denied
> The problem is that CoachDB supplies the original copy of local.ini, and it
> is treated as a template for this configuration file. It is placed into
> /usr/local/etc/couchdb/local.ini.sample, and its copy is placed into
> /usr/local/etc/couchdb/local.ini. Everything under /etc is what admin
> configures. Ideally admin can compare local.ini and local.ini.sample and see
> if anything in default configuration was modified compared to the suggested
> sample.
> When the executable itself modifies local.ini too, this makes it very
> confusing. Admin will be confused if he should or shouldn't touch this file.
> My suggestion is that CouchDB should copy local.ini under /var/db/, or
> somewhere else, and write it there. /etc isn't supposed to be writable by the
> process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
