On Feb 10, 4:43 pm, Matt Wilson <[email protected]> wrote: > On Feb 10, 4:27 pm, Christoph Zwerschke <[email protected]> wrote: > > > > > Matt Wilson schrieb: > > > > I'm trying to set up supervisor to control my TG 1.0 app. > > > > supervisor starts the app fine. I see that my app forks off another > > > child process. So when I try to stop my app or restart it, the forked > > > off process is not stopped or restarted. > > > > What am I doing wrong? > > > Try to get some log output. Something like the following should do: > > > [program:webapp] > > command=env USER=matt HOME=/home/matt /home/matt/projects...start-myapp > > user=matt > > startsecs=10 > > stopwaitsecs=10 > > log_stderr=true > > logfile=/var/log/webapp-supervisor.log > > > -- Christoph > > I know what the problem is -- the start-myapp script forks itself, so > I have two start-myapp processes running. But supervisor only knows > about the one it started. So when I try to restart my server through > supervisor, supervisor correctly stops the parent process, but the > child remains.
When I changed the server.environment setting from "development" to "production", now I don't see that second child process and everything works fine. Is there any page that documents the purpose and effects of all the configuration settings? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
