On Wed, Feb 4, 2009 at 12:36 AM, Kevin Baker <[email protected]> wrote:
> So are you saying that it is doing a restart when it detects a change... > not just reloading the conf? > > If that is the case I guess I can just restart. > > I am trying to reload with as little impact on uptime as possible. With > apache I do a /etc/init.d/apache2 reload rather than restart for the same > effect. > Yes, that's how it works. Apache actually works similarly, but it's a multi-process system -- when it reloads the configuration it makes sure all incoming requests are finished, holds any new incoming requests, and kills all the child processes and then new processes are made with the new configuration. If you have a process in front of the Pylons process you can avoid interruption, so long as the thing proxying to the process will do a retry. I don't think mod_proxy does this, but FastCGI/SCGI and maybe some other setups will do so. -- Ian Bicking | http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
