ot; <[EMAIL PROTECTED]>; "zope-dev"
<[EMAIL PROTECTED]>
Sent: June 15, 2000 01:57 PM
Subject: RE: [Zope-dev] Logging for ZScheduler?
> On Thu, 15 Jun 2000, Loren Stafford wrote:
>
> > Aha! Even tho a cohosted account might not be able to modify the source
of
> >
"Phillip J. Eby" <[EMAIL PROTECTED]>
>
> At 01:58 PM 6/15/00 +1000, Stuart 'Zen' Bishop wrote:
> >
> > Its not a problem with ZScheduler, it a problem that no one has
> > written a plug-in logging system that is good enough for what
> > you are trying to do. The existing zLOG API is fine (well -
Loren Stafford wrote:
>
> Not knowing what subsystem was for, I just filled it with __name__. So a log
> entry looks like this:
>
> --
> 2000-06-14T20:05:22 INFO(0) Products.ZScheduler.Loggerr
> Trigger event: http://eagle:8080/zev3
> Trigger time: 1970/12/31 16:00:00 US/Pacific
> Bang!
>
[EMAIL PROTECTED]]On Behalf
> Of Stuart 'Zen' Bishop
> Sent: Thursday, June 15, 2000 13:52
> To: Loren Stafford
> Cc: Loren Stafford; zope-dev
> Subject: RE: [Zope-dev] Logging for ZScheduler?
>
>
> On Thu, 15 Jun 2000, Loren Stafford wrote:
>
> > > It wou
- Original Message -
From: "Loren Stafford" <[EMAIL PROTECTED]>
To: "Phillip J. Eby" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Loren
Stafford" <[EMAIL PROTECTED]>
Cc: "zope-dev" <[EMAIL PROTECTED]>
Sent: Thursday
On Thu, 15 Jun 2000, Loren Stafford wrote:
> > It would be a good idea if there was a field in the ZEvent that defined
> > the subsystem used in the zLOG call.
>
> I didn't follow your point here. By "subsytem" do you mean which logger in
> the loggers tuple? Then do you mean that different ZEve
On Thu, 15 Jun 2000, Loren Stafford wrote:
> Aha! Even tho a cohosted account might not be able to modify the source of
> the Zope implementation directly, installing a CustomLog product could do so
> indirectly, by importing ZLogger and modifying the loggers tuple. To know
> where to write the l
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Phillip J. Eby
> Sent: Wednesday, June 14, 2000 21:21
> To: [EMAIL PROTECTED]; Loren Stafford
>
> At 01:58 PM 6/15/00 +1000, Stuart 'Zen' Bishop wrote:
> >
> >Its not a problem with ZScheduler, it a pro
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Stuart 'Zen' Bishop
> Sent: Wednesday, June 14, 2000 20:58
> To: Loren Stafford
>
> On Wed, 14 Jun 2000, Loren Stafford wrote:
>
> > I need some advise for designing a flexible system for logging the
>
At 12:42 PM 6/15/00 -0400, Shane Hathaway wrote:
>
>Agreed; I see this as by far the best approach. It's a tried and true
>pattern.
>
Not only that, but it gives you extremely fine-grained control over what
you do and don't log. And, if the other events like adds and deletes on
folders are in p
"Phillip J. Eby" wrote:
>
> At 01:58 PM 6/15/00 +1000, Stuart 'Zen' Bishop wrote:
> >
> >Its not a problem with ZScheduler, it a problem that no one has written
> >a plug-in logging system that is good enough for what you are trying to
> >do. The existing zLOG API is fine (well - it could be bett
At 01:58 PM 6/15/00 +1000, Stuart 'Zen' Bishop wrote:
>
>Its not a problem with ZScheduler, it a problem that no one has written
>a plug-in logging system that is good enough for what you are trying to
>do. The existing zLOG API is fine (well - it could be better), but just
>needs someone to write
On Wed, 14 Jun 2000, Loren Stafford wrote:
> I need some advise for designing a flexible system for logging the
> activities of scheduled events.
You could just call Zope's logging system and move it out of the
scope of your product. Have a look at zLOG.py or LOGGING.txt
if you havn't already. M
I need some advise for designing a flexible system for logging the
activities of scheduled events.
One of the motivations for developing ZScheduler was to have a platform
independent means for scheduling Zope tasks. The lask of a cron on Windows
platforms was a part of the problem. ZScheduler ach
14 matches
Mail list logo
