Hi, The options are Erlang specific. Here are some short descriptions (they are pretty much self-explanatory):
1. Erlang option "-noshell" specifies that no shell is attached to the CouchDB application. 2. Erlang option "-noinput" specifies that once started, you cannot interact with the application but only by the means of its design and purpose. 3. Erlang option "-os_mon" specifies usage of operating system monitor for hardware. 4. OS monitor option "start_memsup" refers to RAM usage supervision. 5. OS monitor option "start_cpu_sup" refers to CPU usage supervision. 6. OS monitor option "disk_space_check_interval" specifies how often the harddisk must be polled for its space usage (in minutes). 7. OS monitor "disk_almost_full_threshold" rings the alarm when a certain HDD usage threshold has been reached. 8. Erlang option "-sasl errlog_type error" specifies usage of SASL (Simple Authentication and Security Layer) logging type set to error (meaning, it will report only when errors will appear). More info at: 1. http://www.erlang.org/documentation/doc-5.1/lib/os_mon-1.5.0/doc/html/os_mon.html 2. http://www.erlang.org/doc/man/erl.html CGS On Thu, Jun 21, 2012 at 3:35 PM, Thomas Hommers <[email protected]>wrote: > Hi, > > I am investigating a problem that my couchDB (1.2.0 on Debian Squeeze > build with build-couchdb) is constantly restarting. > > Along the way I found that it's started with the following parameters. Are > there resources anywhere what they mean, or could somebody explain? > > -noshell -noinput -os_mon start_memsup false start_cpu_sup false > disk_space_check_interval 1 disk_almost_full_threshold 1 -sasl errlog_type > error > > Thanks. > Thomas
