Hello Lars,
Did you read that :
https://github.com/web2py/web2py/blob/0d646fa5e7c731cb5c392adf6a885351e77e4903/examples/logging.example.conf
I am looking at logging rigth now a new module and I do my research...
Setting global logger might be one of the main reason of your issue as I
guess you a
where do I put logging.exception('got exception') and where do I set file
path and name?
2015-01-28 13:41 GMT+01:00 Leonel Câmara :
> You can use logging.exception('got exception')
>
> However, try/exception is generally a bad practice, that catches at any
> exception at all and can lead to very
Thanks I'll explore this route.
On Sun, Feb 17, 2013 at 7:14 PM, Massimo Di Pierro <
massimo.dipie...@gmail.com> wrote:
> Yes I assumed both apps are written in web2py. Yet the protocol it uses is
> CAS 2.0 therefore that works even if application A is not written in web2py
> as long as it suport
Yes I assumed both apps are written in web2py. Yet the protocol it uses is
CAS 2.0 therefore that works even if application A is not written in web2py
as long as it suports CAS 2.0.
Another possibility is, if application A runs under apache, to use the
server access control to delegate authenti
Hi Massimo,
I'm going to explore this option more. Just a quick question though. It
seems like both application A and B need to be web2py. Is that true?
Application A isn't a web2py application.
Also I learned more about the client's criteria -- they mostly just want a
form on application A's
great!
thk
2013/1/8 Niphlod
> if you dind't change the default settings, you can find already a line for
> every log-in action into the auth_event table.
>
> Il giorno martedì 8 gennaio 2013 12:53:16 UTC+1, Ramos ha scritto:
>
>> hello
>> how do i log each time a user logs in?
>>
>> thank you
>>
I've always wondered that, too. It's the one reason I don't put more
functionality in modules.
I'm using this logging module with logging.conf. It works fine in
controllers & models. How to make it work in modules?
Regards,
Joseph
web2py.py -F profiler.log
2011/2/21 NetAdmin
> Maybe you could use a trigger on update, insert or delete, but I'm not
> sure how to do it for a simple "select" statment.
>
>
> On Feb 21, 4:26 pm, Stef Mientki wrote:
> > hello,
> >
> > is there a way to log the time-duration of all sql statement
On Aug 18, 2010, at 6:36 AM, Yarin wrote:
>> The reason for named loggers is twofold. One is trivial: to identify the
>> source of log messages.
> Logging already tracks module, function, lineno... we can even insert
> a stack trace
>> The other ... to let us have different log levels for differe
On Aug 17, 2010, at 9:16 PM, Yarin wrote:
> @Jonathan- Like your use of config files for default configurations,
> but beyond that I'm not clear on what your patch is meant to solve-
> What's your reason for introducing named loggers and sub-loggers at
> the site level? Couldn't the root logger j
On Aug 16, 2010, at 5:25 PM, Yarin wrote:
> @Jonathan- I'd like to see what you've got- keep me updated
The patch is here, if anyone would like to review it.
http://web.me.com/jlundell/filechute/logging.zip
Most of the changes are to use a specific logger instead of making a generic
logging ca
12 matches
Mail list logo
