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

Re: Bug: svnserve fail to detect it is already running

From: Lorenz <lorenznl_at_yahoo.com>
Date: Fri, 09 Jul 2010 06:25:20 +0000

Stefan Sperling wrote:
>LAMBERT DAVID LD wrote:
>> On Windows Server 2003 R2, when svnserve is launched from the command
>> line prompt, and a svnserve is already running, the command keep running
>> indefinitly.
>>
>> It should instead stop and display an error message saying it's already
>> running.
>>
>> The current behavior of this command let user thinks the server is
>> running.

and that it is

>The behaviour you describe seems to be specific to Windows.
>I cannot reproduce it on UNIX. When svnserve tries to bind to a port
>that is already used by another instance of svnserve (or any service
>for that matter), it exist with an error.
>
>$ svnserve -d -r /tmp/repos
>subversion/svnserve/main.c:739: (apr_err=48)
>svnserve: Can't bind server socket: Address already in use
>
>Do you not see this on Windows, too?

just checked, and no there is no error message.
Instead the newly started server blocks / hides the allready running
one.
In my case I have one server running as a windows service, serving a
repo from a folder on my C: drive.
If I start a second svnserve from the command line, pointing it to a
different folder, but listening on the the same port, that prevents
access to the server running as a service.
Aborting the second svnserve will allow access to repo again.

So yes, there seems to be a bug in the windows version (1.6.5 by the
way)

....

After upgrading to 1.6.12 (SlikSVN) I still can start multiple servers
using the same port, but now the server started first seems the have
priority.

...

make that: the server running as a service seems to have priority.

-- 
Lorenz
Received on 2010-07-09 08:29:19 CEST

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