Dieter's point about not includeing the traceback makes sense
if all it does is report on the reporting code.

Wlorent, do you envision a single ConflicError or two -- one which
succeeds on retry and another where the retry fails?


On Sun, 4 Dec 2005, Dieter Maurer wrote:

> Florent Guillaume wrote at 2005-12-2 22:59 +0100:
> > ...
> >If you look at the way their purpose is explained in zLOG, you'll see  
> >that level INFO is reserved for things like server startup and  
> >shutdown.
> >Or, as shown above, initial mounting of databases. Anything  
> >recurring that can happen many times in the life of the server but  
> >does not pose any problems should *not* be visible at INFO.
> 
> Really?
> 
> You infer that from the
> 
>   "INFO  For things like startup and shutdown", do you?
> 
> That's very weak reasoning...
> 
>   The level obviously has an importance association:
>   higher values indicate higher importance.
> 
> 
> If fact, the "ConflictError" messages should not be reported
> at "INFO" but at level "PROBLEM" because
> 
>    they are not causing any immediate problems, but
>    deserve attention.
> 
> >On the other hand, that's exactly what BLATHER is for folks! Use it!  
> 
> You see it this way. I do not:
> 
>   "ConflictError"s are definitely as important as mount
>   messages and therefore should be reported on at least
>   the level of mount reports: i.e. at INFO or above.
> 
> 

-- 

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to