[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: LAMBERT DAVID LD <David.ld.Lambert_at_alcatel-lucent.com>
Date: Thu, 8 Jul 2010 18:30:55 +0200

Hi Stephan,

I cannot see this behavior.
Instead, the command is blocked. I don't get the error message.

David

-----Original Message-----
From: Stefan Sperling [mailto:stsp_at_elego.de]
Sent: jeudi 8 juillet 2010 17:18
To: LAMBERT DAVID LD
Cc: dev_at_subversion.apache.org
Subject: Re: Bug: svnserve fail to detect it is already running

On Thu, Jul 08, 2010 at 04:21:33PM +0200, LAMBERT DAVID LD wrote:
> Hi,
>
>
>
> I'd like to submit the following bug about SVN server :
>
> 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.

Hi David,

I don't think we should generally limit the number of svnserve
processes on a single computer to 1. What if I want to run multiple
instances of svnserve on the same server, each listening on a different
port?

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?

Thanks,
Stefan
Received on 2010-07-08 19:26:12 CEST

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