I am currently running pylons using mod_wsgi, as a daemon process
running as a separate user from apache. I am having problems logging
to anything under mod_wsgi. Any special config needed to log under
mod_wsgi. The logging works fine as a separate process, however not
using mod_wsgi. Any Ideas?
> If the logging system you are using is trying to output to sys.stdout
...
No, I am not logging to stderr or stdout
> If not using sys.stdout but a file of your own as output for logging,
> also be aware that you can't use relative path names for files as when
> using Apache there isn't really a
On Nov 15, 10:51 pm, PyDevler <[EMAIL PROTECTED]> wrote:
> How I performed this, was
> using the standard pylons config, which uses the python config for
I have attached my config, maybe there is something missing here.
Excerpt from pr
> What does the WSGI script file for mod_wsgi that you are using
> contain?
It contains the one line that was documented.
[code]
import os, site; site.addsitedir(eggs_dir)
from paste.deploy import loadapp
application = loadapp('config:Path.../production.ini' )
[/code]
--~--~-~--~~--
When I previously mentioned invistigating. I managed to get it to log
by manually adding a handler from within my controller-xyz.py. However
it is refusing to load my config. It is for some reason refusing to
use the Formatter line, that I adjust from within controller-xyz.py.
However, it changes
> In the documentation for Pylons logging it says:
>
> """paster, when loading an application via the paster serve, shell or
> setup-app commands, calls the logging.fileConfig function on that
> specified ini file if it contains a 'loggers' entry.
> logging.fileConfig reads the logging configurati
Hi James,
On Jul 11, 10:21 pm, Eric Ongerth <[EMAIL PROTECTED]> wrote:
> Visually: looks great! Good work.
I agree the book looks great. I had a question about how you are
maintaining
it. If you don't mind me asking, is it written in "latex",
"RST", ... . Also
how is it being converted to HTML
