of course the syslog-ng makes sense only for the scheduler (but, if you're using uwsgi with multiple processes, syslog-ng is the only handler that works without issues, for the exact same "limitation") Logging into database (if not something like mongodb & co.) seems a little bit daunting, given that most of the problems are usually coming from database contention.
I'm not a logging guru, but scheduler "identity" is *web2py.scheduler*.%s % PID so *web2py.scheduler* works fine as qualname [loggers] keys=root,rocket,markdown,web2py,rewrite,cron,app,welcome,scheduler [logger_scheduler] level=INFO handlers=consoleHandler,rotatingFileHandler qualname=web2py.scheduler -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
