[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: FATAL errno=32

From: Jim Hanley <jhanley_at_DGtlRift.com>
Date: Thu, 2 Apr 2009 18:38:35 -0400

I've seen errors like this on a 1.3-something. It had some thing to do
with a timeout big in http. By chance is it a blastwave package for

This is my signature

On Apr 2, 2009, at 6:09 PM, webpost_at_tigris.org wrote:

> I have about 200 svn repositories running on version 1.3.0 (I know I
> need to upgrade because it is not supported, we are in the process
> AWS)
> I have one repository that I get this FATAL error almost every time
> I do an svn up:
> FATAL: output (local) failed, errno=32
> It looks like it finishes the update but the error worries me, does
> anyone have a clue as to what is going on? It is my largest
> repository with 21000 revision.
> Any help would be great,
> Thanks,
> Howard
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1525107
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org
> ].


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-03 00:40:09 CEST

This is an archived mail posted to the Subversion Users mailing list.