On Tue, 09 Dec 2003 12:41:22 -0600, Ben Collins-Sussman
<sussman@collab.net> wrote:
>On Tue, 2003-12-09 at 12:31, olczyk@interaccess.com wrote:
>
>> I'm using the most recent version of Subversion-0.34.0.
>>
>> I've alternately tried
>> svnserve
>> svnserve -r /svn
>
>> (which the book claims is the port that svnserve listens on )
>>
>>
>
>The book also explains that you need to run svnserve as a daemon (-d):
>
>"The alternative is to run svnserve as a standalone daemon. When started
>with the -d option, svnserve will immediately detach from the current
>shell process, and will execute as a background process which runs
>indefinitely, again waiting for incoming requests on port 3690.
>
>$ svnserve -d
>$ # svnserve is still running, but the user is returned to the prompt
>"
It also says:
One option is to register an svn service with the server machine's
inetd. Then, when a client attempts to connect to that machine on
port 3690, 17 inetd will launch a "one-off" svnserve process to handle
that client's request.
Just before that. I misunderstood how the method works since I do not
work with inetd that much.
That begs the question of what the command for inet should look like.
-------------------
svnserve -d, though it works listens at IP address 0.0.0.0
So the next question is how do I get it to listen on the actual
address?
Also the deamon way doesn't indicate how svnserve is shut down.
It would really help there to have the startup and shutdown scripts
/init scripts since the one time I looked, they were really a PIA to
write.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 9 20:06:46 2003