I am running pylons behind an Apache reverse proxy server, at the
commandline, I startup the the paster server:
paster serve development.ini
the terminal console is blocked, on windows, closing the termnal has
no effect, the server runs on, on Linux, the paster server is killed
immediately,
nevermind
running in daemon mode was the key
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this
Actually its easy
paster serve --daemon production.ini
Thats it. I would not advice you to use --reload of you are using
Debian though, it can´t be stopped properly, things like kill process
number don't work, the only thing that did was kill -9, which is
actually taboo
Use Cron to ping and
On Thu, May 31, 2007 at 11:04:33AM -0700, voltron wrote:
Actually its easy
paster serve --daemon production.ini
Thats it. I would not advice you to use --reload of you are using
Debian though,
What makes you draw *that* funny conclusion? I'm developing Pylons
applications on Debian for
On 5/31/07, Christoph Haas [EMAIL PROTECTED] wrote:
And that Debian should be
guilty of suffering from a rare processes get stuck disability sounded
very strange to me, too.
It's a real problem. When paster serve --reload exits, it leaves
worker threads running. This causes an address
