David Kimdon wrote:
...
> My expectation is that in most cases svnserve is used on conjunction
> with ssh or is started via inetd. In that case no init.d script is
> needed
I see what you mean. I didn't realise that was the intention.
..
> Should
> there be a commented entry in /etc/inetd.conf?
That would help. Perhaps an installation configuration question asking
the user whether they want svnserve to be started by inetd would be better?
> If you can describe a bit how you are using svnserve
> we can probably find something that makes sense.
I've created my own /etc/init.d/svn and /etc/default/svnserve
I could post them if you want them.
However, svnserve seems rather lightweight so far, so inetd could be
entirely adequate.
David Kimdon wrote:
...
> My expectation is that in most cases svnserve is used on conjunction
> with ssh or is started via inetd. In that case no init.d script is
> needed
I see what you mean. I didn't realise that was the intention.
..
> Should
> there be a commented entry in /etc/inetd.conf?
That would help. Perhaps an installation configuration question asking
the user whether they want svnserve to be started by inetd would be better?
> If you can describe a bit how you are using svnserve
> we can probably find something that makes sense.
I've created my own /etc/init.d/svn and /etc/default/ svnserve
I could post them if you want them.
However, svnserve seems rather lightweight so far, so inetd could be
entirely adequate.