On Mon, 28 Jul 2008 03:30:55 -0400, Chris McDonough <[EMAIL PROTECTED]> writes:

> Anders Quist wrote:
>> On Fri, 25 Jul 2008 23:22:29 -0400, Chris McDonough <[EMAIL PROTECTED]> 
>> writes:
>> 
>>> I've changed the following:
>>>
>>> - I've removed the reread, avail, and reread commands from supervisorctl
>>>    as they're not quite yet ready for primetime.
>>>
>>> - I removed the backend code from rpcinterface to handle reread, as it
>>>    only computes a diff rather than restarting any processes.
>> 
>> What deficiencies does reread have? If you want to add/remove
>> processes manually, don't you want a way to reload the config file? Or
>> was the implementation objectionable?
>
> I may have misunderstood this. I had assumed that using "add" in
> particular implied that the config file would be reread, and no
> manual reread step would be required before you tried to use "add".
> But maybe it doesn't operate that way. I didn't actually test trying
> to add a program that wasn't already in the config file when
> supervisord started.

I just implemented the primitives for making it possible. I'm not sure
if it makes sense to do an implicit reread. If add does an implicit
reread, you may end up with this:

  > avail
  foo
  > add foo
  foo: no such

since foo was actually not in the config any more. It seems to me that
having an explicit read makes it easier for the user to have a mental
model of the state of supervisord.
-- 
Anders Qvist, Open End AB
Tel: +46 31 7490887

_______________________________________________
Supervisor-users mailing list
[email protected]
http://lists.supervisord.org/mailman/listinfo/supervisor-users

Reply via email to