You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Goetz Golla <Go...@genua.de> on 2005/09/17 14:44:03 UTC
SVN::Client + svnserve children
I am using the SVN::Client functions from various mod_perl/mason scripts on an
apache webserver. SVN::Client is part of libsvn-core-perl, which is part of
debian sarge.
I am also running svnserve to allow access to the svn repository.
The problem is: whenever I run a SVN::Client function, like
my $ctx = new SVN::Client();
...
my $res = $ctx->status($workid, $revision, $status_func, $recursive,
$get_all, $update,0);
it does what it should, but it leaves a svnserve child process running
foreverm with an open tcp connection from apache to svnserve. With serveral
users accessing the website I quickly end up having hundreds of svnserve
processes hanging around. I wonder if there is anything I missed to make
apache / SVN::Client close the connection to svnserve ?
Goetz Golla
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org