$Id: TODO,v 1.12 2003/04/27 16:31:52 david Exp $

zopectl (it works)

 - problem after 'zopectl restart'; "can't start, status is starting' --
   fix that.

 - new Debian policy: restart should start any non-running zopes; -- fix that;
   maybe we should add a restart-running command for the current 
   behavior.

- stuff from/for the changelog not fully implemented yet:

- run zope as root or non-root, based on the ports it will want to
  open (partially coded), based on upstream SETUID suggestions;
  may not be important.

- should zopectl be more explicit (e.g. not quiet about stopping
  nonrunning instances) when given an explicit list of instances?

- add support for --concurrent (partially coded)

- look at and fix all '??' flagged code

- move zopectl.py to a python lib directory, or add a manpage for it

- stop might have to wait for all pids in session to be gone; seems to
   take 'forever' on moe.  Wait for the Data.fs.lock file to
   have a pid?

- similarly, should 'start' wait until the subprocess has reached a
  useable state -- e.g. it has said something (specific?) in the
  event log?  probably not, but maybe should check that the 
  process persists, e.g. that the size of the --sid list
  doesn't decrease for some short time?  nah, too ugly and
  error-prone.  think more about this...  Wait til the
  Data.fs.lock pid has stopped?

- for both of the above, remember that the lock doesn't get
  created in zodb read-only mode; so maybe that's a bad idea.

- status gets permission error when calling SIGNAL 0 on a
  non-owned process -- should we use ps instead for that?
  are there other similar cases?  



zope-make-instance (still in very early development)

- zope-make-instance must set directory ownership and security the way
  z2.py insists on seeing it.

- log file permissions?

- look at and fix all '??' flagged code

other ideas?

- first zope instance could be configured by debconf/postinst; others too?

- Are the instructions and environment variables in debian/Zope.cgi 
  correct?  cf. README.Debian.  Should these be instance-configurable?


