[Zope-Checkins] Re: CVS: Zope/skel/bin - runzope.in:1.1.2.1 zopectl.in:1.1.2.1

[Fred L. Drake, Jr.]

[It looks like RDM meant to CC: his query to zope-checkins, but made a
 typo.  I'm including the list so everyone can join in.]

R. David Murray writes:
 > So this looks to me like you are going to have a 'zopectl'
 > script for every instance?  This is very awkward from a
 > system administration standpoint.  It would be much better to
 > have a central zopectl that you would pass the name/directory
 > of an instance home to, and it would read a config file from
 > that instance to decide what to do.

The per-instance zopectl is just a wrapper around a shared script that
will live in the software installation (ZOPE_HOME/bin/), and makes
sure that the right paths are set up.  It does not preclude using the
general (not instance-specific) zopectl.py script directly, and
passing the right args along to specify the instance.

 > For example, I wrote a 'zopectl' script that does this to ease my
 > own system administration.  It allows me to say
 > 
 >     zopect start all
 > 
 > in my system startup script, and 'all' gets translated into a
 > list of production instances, each of which has a config file that
 > is then read and used to start them up.

Interesting idea; we'll have to think about that.  How do you handle
the mapping?

 > I can of course rewrite this script to call these individual
 > startup scripts, but I thought that one of the goals was to replace
 > the start/stop scripts with configuration files.

All the information needed to describe an instance will be in the
config file, INSTANCE_HOME/etc/zope.conf.  The
INSTANCE_HOME/bin/zopectl script is simply a convenience to let an SA
avoid a bit of typing in the simple case.


  -Fred

-- 
Fred L. Drake, Jr.  <fred at zope.com>
PythonLabs at Zope Corporation