On 8 Nov 2013, at 5:45 AM, Niphlod <niph...@gmail.com> wrote: > the only thing is that only syslog-ng is multiprocess-safe, so the standard > logging to file and/or console may incur in problems.
That applies to more than the scheduler, though, and using syslog isn't so bad. (Maybe we could add a database-based handler?) In any event, the scheduler's current use of pid to distinguish logging facilities is problematic because it can't be configured. Or at least I don't think it can; I don't see any wildcard capability in the logging conf syntax. Have you actually used it? How? > > On Friday, November 8, 2013 5:46:29 AM UTC+1, Jonathan Lundell wrote: > On 7 Nov 2013, at 7:05 PM, Andrew W <awill...@gmail.com> wrote: > >> Thanks. I've never been quite sure what to put in logging.conf for the >> scheduler debug key, based on the "logger =" statement in scheduler.py. > > We should add a schedule section to the logging example file. > -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
