How can I specify the log file for Pyramid ?

2011-06-16 Thread ghosert
I don't see anyway in documentation mentioned this, anyone can post a url will be helpful. And maybe add this part to narrative documentation will be useful for the fresh man. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this

How can I specify the log file for Pyramid ?

2011-06-16 Thread Zhang Jiawei
I don't see anyway in documentation mentioned this, anyone can post a url will be helpful. And maybe add this part to narrative documentation will be useful for the fresh man. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this

Re: How can I specify the log file for Pyramid ?

2011-06-16 Thread Chris McDonough
On Thu, 2011-06-16 at 09:06 +0800, Zhang Jiawei wrote: I don't see anyway in documentation mentioned this, anyone can post a url will be helpful. And maybe add this part to narrative documentation will be useful for the fresh man.

Re: How can I specify the log file for Pyramid ?

2011-06-16 Thread Zhang Jiawei
And actually I hope all the stuffs go to uwsgi log file now, will go to the log file in production.ini I specified. Is this possible ? 2011/6/17 Zhang Jiawei ghos...@gmail.com Thanks Chris. And I have another question about logging. I can start pyramid with uwsgi successfully now, and the

Re: How can I specify the log file for Pyramid ?

2011-06-16 Thread Zhang Jiawei
Thanks Chris. And I have another question about logging. I can start pyramid with uwsgi successfully now, and the logging info is written to the log file I specified path in the production.ini, but I found exceptions raised in view will be logged to the file which is specified by uwsgi not the

Re: How can I specify the log file for Pyramid ?

2011-06-16 Thread Chris McDonough
On Fri, 2011-06-17 at 08:57 +0800, Zhang Jiawei wrote: Thanks Chris. And I have another question about logging. I can start pyramid with uwsgi successfully now, and the logging info is written to the log file I specified path in the production.ini, but I found exceptions raised in view