http://freshmeat.net/projects/log4py/
Romain Slootmaekers wrote:
> Yo,
> questions wrt logging:
>
> -) What are the plans to improve the rather primitive logging facilities
> in zope ?
> I couldn't find anything in the plan for 2.6, nor on the 3.0 homepage.
> I think we need at least an extendi
Romain Slootmaekers wrote:
>
> - Loggers (fi, file logger, db loggers, remote logger, nulllogger,...)
Zope already has a filer logger, I dunno what you mean by db, remote and null loggers,
perhaps you can explain?
> - Filters (fi on severity, on subsystem, ...)
zLOG already provides this.
Se
On Fri, 1 Mar 2002, Chris Withers wrote:
> Romain Slootmaekers wrote:
> >
> > - Loggers (fi, file logger, db loggers, remote logger, nulllogger,...)
>
> Zope already has a filer logger, I dunno what you mean by db, remote and null
>loggers,
> perhaps you can explain?
>
db= log to database..
Romain Slootmaekers <[EMAIL PROTECTED]> writes:
> db= log to database...
>
> remote:what if you want your logs to be put on another machine
>
> null logger does nothing.
Handling the log output should be _completely_ separated from
Zope.
On the fly changes to log levels and separating oupu
Have you looked at EventLogManager?
http://www.zope.org/Members/mcdonc/Products/EventLogManager
If I had it to do over again, I'd change lots, but it does do what you're
asking for.
> what if I want to split the logs based on some condition
> I have to change code in Zope, and restart the se
Romain Slootmaekers <[EMAIL PROTECTED]> writes:
> > Handling the log output should be _completely_ separated from
> > Zope.
> what do you mean exactly by '_completely_ separated'
>
> do you mean asynchronous handling ?
Completely separated means that it isn't Zope's job to care for rotating
log
On 01 Mar 2002 16:27:18 +0100, Frank Tegtmeyer <[EMAIL PROTECTED]>
wrote:
>Completely separated means that it isn't Zope's job to care for rotating
>logs, filtering them and what else you could do to logs. There are
>lots of programs out there that are specialized in handling log data.
>
>We for
See PEP 282 [1]. If this PEP is accepted, work should probably follow its
course. It would be nice to have a single logging mechanism for Python, and
for Zope to use and/or extend it. Granted, if it is accepted, it won't be
in Python until Python 2.3 which I believe is due in August.
..[1] htt
Toby Dickenson <[EMAIL PROTECTED]> wrote:
> Or the humble syslog, which is good enough to keep me happy at the
> moment.
Except that syslog (with all its faults) is designed for reliable
logging, which means that if you send to your log 1000 lines, syslog
will sync 1000 times thus trashing your
Florent Guillaume writes:
> Except that syslog (with all its faults) is designed for reliable
> logging, which means that if you send to your log 1000 lines, syslog
> will sync 1000 times thus trashing your disks.
Decent "syslog" implementations (such as the one distributed with
SuSE Linux) let
10 matches
Mail list logo
