I noted that and will upgrade in this round.  It's the old problem of 
having live systems, distributed development, and all.  The usual 
groundrules are: only transparent changes, no risk of errors, no 
disruption of 24x7 use, etc.


On Wed, 25 May 2005, Paul Winkler wrote:

> On Wed, May 25, 2005 at 09:15:32AM -0700, Dennis Allison wrote:
> > 
> > Furher investigation has shown that the failing ZSyncer target had a 
> > problem with its authentication code and that was likely the cause of 
> > the failure.  We are continuing to test, but it appears everything is 
> > working.   We'll continue to test but I am pretty sure this was not a 
> > ZSyncer problem.
> 
> You might be interested to know that I made substantial improvements
> to the error reporting and logging for ZSyncer 0.6.
> Problems like this are generally easier to diagnose now.
> 
> -PW
> 
> 

-- 
Dennis Allison * Computer Systems Laboratory * Gates 227
               * Stanford University *  Stanford CA  94305
               * (650) 723-9213 * (650) 723-0033 fax
               * [EMAIL PROTECTED]
               * [EMAIL PROTECTED]


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

Reply via email to