You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Jan Lehnardt (Closed) (JIRA)" <ji...@apache.org> on 2011/10/30 22:24:32 UTC

[jira] [Closed] (COUCHDB-501) launchd plist for Mac OS X needs cleanup

     [ https://issues.apache.org/jira/browse/COUCHDB-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Lehnardt closed COUCHDB-501.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.10

This has been fixed long ago. Closing.
                
> launchd plist for Mac OS X needs cleanup
> ----------------------------------------
>
>                 Key: COUCHDB-501
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-501
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: 0.11
>         Environment: Mac OS X 10.6, Snow Leopard
>            Reporter: Per Ejeklint
>            Priority: Minor
>             Fix For: 0.10
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> The provided org.apache.couchdb.plist for launchd contains the flag OnDemand set to true, as well as KeepAlive. OnDemand was deprecated in 10.4 and replaced by KeepAlive which is much more powerful. As a result, launchd will NOT restart CouchDB on Snow Leopard after it has been stopped with launchctl stop org.apache.couchdb, as is stated in the README. A manual start or reboot is needed.
> Solution: just remove the OnDemand tag from the plist and all is happy happy again.
> As a side note: if on-demand loading is really what's wanted, launchd needs more information. There must be information about which socket launchd should monitor, and keeping that in sync with the port number people choose for couchdb seems just way too much work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira