On Tue, Apr 26, 2005 at 01:40:12PM +0200, Marcus Rueckert wrote:
> On 2005-04-26 08:52:31 +0200, Tom Rune Flo wrote:
> > One reason would be if you want to start svnserve automatically during
> > boot time, as you probably do with most of your other daemonized servers.
> >
> > You could of course write some sort of wrapper for this, but to me it
> > makes a lot more sense for svnserve to be able to set uid/gid by itself.
>
> just some examples:
> # suse
> $ startproc -u svn -g svn -e /usr/bin/svnserve -d -r /srv/svn/repositories
>
> # debian
> $ start-stop-daemon --start --chuid svn --group svn --exec /usr/bin/svnserve -- -d -r /srv/svn/repositories
>
> # general
> sudo -u svn "/usr/bin/svnserve -d -r /srv/svn/repositories"
>
> i think this are enough solutions which all work.
I'm sure they work, if you run suse, debian or have sudo installed on you
system. I don't, and I probably never will. But that is beside the point.
I'm not interested in a lengthy discussion, and I would guess that neither
are you, but I would like to point this;
My server is currently running quite a number of different services,
every single one of them, except svnserve, is self-supporting enough
to be started at boot time without wrappers or "3rd party" tools.
I really cannot see why svnserve should be different. Yes, one can use
sudo, daemontools, inetd, all kinds of wrappers -- but should that really
be necessary for a "daemonized" server? What is the difference between
svnserve (running with the -d option) and apache, or sshd?
Well, that's it for me on this issue. Thanks for your time.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 26 18:45:06 2005