[ZCM] [ZC] 2318/ 2 Resolve "Allow override of zopectl control socket"

Issue #2318 Update (Resolve) "Allow override of zopectl control socket"
 Status Resolved, Zope/bug+solution medium
To followup, visit:
  http://www.zope.org/Collectors/Zope/2318

==============================================================
= Resolve - Entry #2 by tseaver on Apr 30, 2007 1:37 pm

 Status: Pending => Resolved

Patch applied to the 2.8 branch:

 http://svn.zope.org/Zope/branches/Zope-2_8-branch/?rev=74935&view=rev

the 2.9 branch:

 http://svn.zope.org/Zope/branches/2.9/?rev=74937&view=rev

the 2.10 branch:

 http://svn.zope.org/Zope/branches/2.10/?rev=74938&view=rev

and the trunk:

 http://svn.zope.org/Zope/trunk/?rev=74939&view=rev
________________________________________
= Request - Entry #1 by tseaver on Apr 30, 2007 12:41 pm


Uploaded:  "zopectl_sockname_override.patch"
 - http://www.zope.org/Collectors/Zope/2318/zopectl_sockname_override.patch/view
The zdaemon subclass used by zopectl does not allow setting the
control socket it uses to talk to the daemonized child process;
it hardwires the location of that socket to:

  $INSTANCE_HOME/var/zopectlsock

The attached patch adds a key to the '<zoperunner>' section, along
with handler code, to enable overriding this socket path, as can
be done currently with the corresponding ZEO server config.  Such
an override would look like:

  <zoperunner>
    socket-name /var/run/zopectl.sock
  </zoperunner>

The patch is made against the Zope 2.10 branch, and applies cleanly
to the 2.8 branch, the 2.9 branch, and the trunk.
==============================================================