You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Eric Seppanen <ed...@reric.net> on 2005/02/03 01:09:20 UTC
strange behavior during scripted propset
I'm experiencing some strange behavoir with subversion 1.1.3 on Linux.
A while back I started a subversion repository with a script that
checked in a year's worth of code changes, and now I want to go back and
set the author to "unknown" so that it's obvious for the old code that
it wasn't all mine.
Here's the interesting part:
bash$ for ii in `seq 3 35`; do svn propset -r $ii \
--revprop svn:author "unknown"; done
property 'svn:author' set on repository revision 3
property 'svn:author' set on repository revision 4
property 'svn:author' set on repository revision 5
/ snip many lines /
property 'svn:author' set on repository revision 25
property 'svn:author' set on repository revision 26
property 'svn:author' set on repository revision 27
svn: Connection closed unexpectedly
svn: Can't connect to host 'blah.blah.com': Connection refused
svn: Can't connect to host 'blah.blah.com': Connection refused
svn: Can't connect to host 'blah.blah.com': Connection refused
svn: Can't connect to host 'blah.blah.com': Connection refused
If I try to run it again immediately, I immediately get "Connection
refused" messages. If I run "svn status", it resets and I can again run
27 propsets before it blows up. So that says to me that it's not a lack
of file descriptors or something... it must be related to Subversion.
It's connecting to svnserve on the same machine.
Any ideas?
Thanks, Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: strange behavior during scripted propset
Posted by Eric Seppanen <ed...@reric.net>.
I'm not using Apache, I'm using svnserve.
But actually, putting sleep in the loop does improve the situation.
Takes forever to run, though.
I'm still interested in finding out what's wrong... if my database is
broken or fragile I'd rather fix it now than wait for something bad to
happen.
On Thu, Feb 03, 2005 at 08:27:48AM -0500, Dale Worley wrote:
> I've seen behavior like this when Apache was accidentally set to throttle
> traffic when there were too many requests from a single source. If you put
> "sleep 1" in the loop, do you see the same thing?
>
> Dale
>
> -----Original Message-----
> From: Eric Seppanen [mailto:eds@reric.net]
> Sent: Wednesday, February 02, 2005 8:09 PM
> To: users@subversion.tigris.org
> Subject: strange behavior during scripted propset
>
>
> I'm experiencing some strange behavoir with subversion 1.1.3 on Linux.
> A while back I started a subversion repository with a script that
> checked in a year's worth of code changes, and now I want to go back and
> set the author to "unknown" so that it's obvious for the old code that
> it wasn't all mine.
>
> Here's the interesting part:
> bash$ for ii in `seq 3 35`; do svn propset -r $ii \
> --revprop svn:author "unknown"; done
> property 'svn:author' set on repository revision 3
> property 'svn:author' set on repository revision 4
> property 'svn:author' set on repository revision 5
> / snip many lines /
> property 'svn:author' set on repository revision 25
> property 'svn:author' set on repository revision 26
> property 'svn:author' set on repository revision 27
> svn: Connection closed unexpectedly
> svn: Can't connect to host 'blah.blah.com': Connection refused
> svn: Can't connect to host 'blah.blah.com': Connection refused
> svn: Can't connect to host 'blah.blah.com': Connection refused
> svn: Can't connect to host 'blah.blah.com': Connection refused
>
> If I try to run it again immediately, I immediately get "Connection
> refused" messages. If I run "svn status", it resets and I can again run
> 27 propsets before it blows up. So that says to me that it's not a lack
> of file descriptors or something... it must be related to Subversion.
>
> It's connecting to svnserve on the same machine.
>
> Any ideas?
>
> Thanks, Eric
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: strange behavior during scripted propset
Posted by Dale Worley <dw...@pingtel.com>.
I've seen behavior like this when Apache was accidentally set to throttle
traffic when there were too many requests from a single source. If you put
"sleep 1" in the loop, do you see the same thing?
Dale
-----Original Message-----
From: Eric Seppanen [mailto:eds@reric.net]
Sent: Wednesday, February 02, 2005 8:09 PM
To: users@subversion.tigris.org
Subject: strange behavior during scripted propset
I'm experiencing some strange behavoir with subversion 1.1.3 on Linux.
A while back I started a subversion repository with a script that
checked in a year's worth of code changes, and now I want to go back and
set the author to "unknown" so that it's obvious for the old code that
it wasn't all mine.
Here's the interesting part:
bash$ for ii in `seq 3 35`; do svn propset -r $ii \
--revprop svn:author "unknown"; done
property 'svn:author' set on repository revision 3
property 'svn:author' set on repository revision 4
property 'svn:author' set on repository revision 5
/ snip many lines /
property 'svn:author' set on repository revision 25
property 'svn:author' set on repository revision 26
property 'svn:author' set on repository revision 27
svn: Connection closed unexpectedly
svn: Can't connect to host 'blah.blah.com': Connection refused
svn: Can't connect to host 'blah.blah.com': Connection refused
svn: Can't connect to host 'blah.blah.com': Connection refused
svn: Can't connect to host 'blah.blah.com': Connection refused
If I try to run it again immediately, I immediately get "Connection
refused" messages. If I run "svn status", it resets and I can again run
27 propsets before it blows up. So that says to me that it's not a lack
of file descriptors or something... it must be related to Subversion.
It's connecting to svnserve on the same machine.
Any ideas?
Thanks, Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org