Sajesh Singh wrote: > >Strangest thing. I left mailman alone last night and when I can in this >morning and ran another test without making any other configuration >changes it worked. Could it be that one of the nightly cron jobs is >running a command that I need to run after making changes to the .py files ?
Not exactly. When the qrunners are started by the master mailmanctl process, they import (and cache) all the mailman modules they use. Thus, whenever you make changes to any *.py modules, you need to do bin/mailmanctl restart to make sure that the changed modules will get recompiled and reloaded into all processes. If the changed module had not been recompiled, it is quite likely that a cron job referenced it and forced the recompile, but I'm not sure whether this in itself would have caused it to be reloaded into the cache of the qrunner processes or if some other event triggered it. The answer is as I said above. Any time you change any *.py files, do bin/mailmanctl restart when you're done. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
