hi there i can confirm this. having (most probably) the same issue with changing limits for memmon - see the thread http://lists.supervisord.org/pipermail/supervisor-users/2010-February/000527.html
using supervisor 3.0a9 in the meantime the problem is still the same. as a workaround i need to rename the group, reread configuration, remove the old group and reread, restart again. regards, harald Am Mittwoch, 8. Dezember 2010, um 23:38:34 schrieb Yang Zhang: > Couldn't report this as a bug on the collector as registration is disabled. > > Using supervisor 3.0a8, `supervisorctl reread` doesn't pick up changes > to supervisord.conf that seem reasonable for it to pick up. > > For instance, after changing `events=PROCESS_STATE_STARTING` to > `events=PROCESS_STATE_RUNNING`, and after restarting that event > listener, it continues to receive PROCESS_STATE_STARTING events only. > -- > Yang Zhang > http://yz.mit.edu/ > _______________________________________________ > Supervisor-users mailing list > [email protected] > http://lists.supervisord.org/mailman/listinfo/supervisor-users > -- Webmeisterei GmbH - Büro für Netzfragen Tel: +43 5572 908877, Fax: +43 5572 908877-66 Steinebach 18, A-6850 Dornbirn http://www.webmeisterei.com _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
