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

[Book] svnserve+inetd configuration is incorrectly described

From: Marcin Kasperski <Marcin.Kasperski_at_softax.com.pl>
Date: 2004-03-02 15:32:25 CET

(book rev 8581, page 83, chapter 'svnserve, a custom server')

The book seems to be suggesting that bare adding
    snvserve 3690/tcp
to the /etc/services will cause snvserve to be runned by inetd. This is
plainly wrong, here we just create symbolic name for the port 3690.

Instead, to have svnserve running from inetd one need to:

- create some Unix account (I'd recommend suggesting the standard name -
say svnowner), create repository on this account

- edit /etc/services as described above (optional)

- edit /etc/inetd.conf and add the line

svnserve stream tcp nowait svnowner /usr/local/bin/svnserve -i -d
/repositories

or (if using TCPwrappers)

svnserve stream tcp nowait svnowner /usr/sbin/tcpd
/usr/local/bin/svnserve -i -d /repositories
(plus corresponding edition of /etc/hosts.allow or /etc/hosts.deny)

- running kill -HUP <inetd-pid>

It is also worth noting that running CVS pserver from inetd happened to
fail during large commits/updates due to inetd limits on the connect
count, I do not know whether this can relate to subversion too (this is
the question whether running large svn checkout/update/commit causes a
lot of connections to be made or keeps using single connection for the
repetitive files/directories).

Considering svnserve is intended as 'first-entry' repository access
method, I'd spent some time on this chapter...

BTW: reporting book bugs would be easier if the book sections were
numbered...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 2 15:31:41 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.