how about creating a new Logger like turbogears.log.local_debug and
add a handler for that that assigns the msg to some local var which
gets included in the output. that way you get the msg both in the
output and in your log files.
On 7/26/07, venkatbo <[EMAIL PROTECTED]> wrote:
>
> Hi folks,
>
> 'am wondering if the best way to change the log level at runtime, is
> to provide a link in page, which when clicked, changes the current
> logger's level: log.setLevel(...) and have an immediately for the
> activity for all logged in users.
>
> Also, is there a built-in option to be able to read (like tail) the
> last n-lines of a log (app-log, and acees-log being generated).
> Preferably, what would help debugging, is:
> . click on a link in the webpage indicating level change to say
> DEBUG
> . have the controllers do their thing after changing the level -
> possibly
> leave a BEGIN/END marker in the log, and returning just that
> snippet,
> possibly appended to the bottom on the response.
> Would help remote debugging etc.
>
> Thanks,
> /venkat
>
>
> >
>
--
cheers
elvelind grandin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
