see below ...
Peter N. Lundblad wrote:
> On Tue, 4 Oct 2005 email@example.com wrote:
>> i have a problem using TortoiseSVN (but the same problem also appeared with
>> subclipse). I've reported the problem already on the
>> TortoiseSVN-mailinglist and also got an answer (blaming svnserve),
>> see for my data about my environment, tcpdumps, etc:
>> got the following answer:
>> The answer states that in an older subversion (as i am using), there
>> is/was a problem with forked svnserve-instances that do not disappear, and
>> so "blocking" the SVN-server for further client-calls. I've again tested
>> it and indeed, those additional svnserve-processes are forked on the
>> server, and don't disappear. That causes the server to hang for further
>> Can you please help me, i'm running out of ideas, what i can do to fix or
>> avoid this situation. We wanted to use SVN as versioning system here
>> at our group at the university. But it's not possible to use it with this
> If the bug is in an old version of Subversionm, then why don't you try the
> latest version?
Because they have a rather strict policy regarding the installing of
Suse-RPMs here. They only want to rely on the "official" Suse-RPMs
and subversion-1.1.3-10 was the latest package available.
I also tested it with subversion-1.2.1 on another only-test-system,
but it showed up the same problem, and i was instructed to get it
to work with the "official" RPMs.
The guy from Tortoise said, he remembered a problem with "blocking/
hanging" svnserve-processes but couldn't remember exactly. Can you
approve or deny that ?
Jens-Uwe Gaspar Schlund + Partner AG
E-Mail: firstname.lastname@example.org Brauerstr. 48
Tel. +49-721-91374-50 76135 Karlsruhe, Germany
Fax +49-721-91374-20 http://www.schlund.de
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Oct 5 18:05:45 2005