[ https://issues.apache.org/jira/browse/COUCHDB-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893424#action_12893424 ] 

Randall Leeds commented on COUCHDB-839:
---------------------------------------

I've brought this up a couple of times and it was shot down for the following reason.

On a system that utilizes /etc/defaults/couchdb or similar you can export ERL_FLAGS or ERL_AFLAGS environment there. Similarly, you can export ERL_MAX_PORTS or ERL_MAX_ETS_TABLES directly rather than pass them as flags.

On a less straightforwardly supported init setup it's on you to create your own wrapper script to do this.

> [PATCH] Couchdb startup script should support a erl startup options flag
> ------------------------------------------------------------------------
>
>                 Key: COUCHDB-839
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-839
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Build System
>    Affects Versions: 0.11.1
>         Environment: Linux, cent-os, any
>            Reporter: Chris Stockton
>            Priority: Minor
>         Attachments: couchdb.tpl.in.patch
>
>
> It seems that the couchdb script does not support any options to pass to the erlang vm. Would be nice to allow a options flag and document on the wiki that it exists. It is important because large-scale deployments of couchdb need to pass some limits on to erlang. For example, I am using a -O option of: -O "+P 65536 -env ERL_MAX_ETS_TABLES 60000 -env ERL_MAX_PORTS 60000"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.