Doesn't 'svnserve --log-file' handle this?
Clients run 'ssh $host svnserve -t' by default, so you'd have to make
that invocation spawn an svnserve that has --log-file passed to it. You
could alter the svnserve in $PATH or use sshd configuration
(ForceCommand and command="" directives) to achieve that.
Nico Kadel-Garcia wrote on Fri, Apr 01, 2011 at 21:45:47 -0400:
> On Fri, Apr 1, 2011 at 5:03 PM, Eric <spamsink_at_internetsmallfry.com> wrote:
> > At 04:51 PM 4/1/2011, Chris Shelton wrote:
> >
> >>>>>>
> >>
> >> If you are using apache for serving your repository,
> >
> > <<<<<
> >
> > Good afternoon, Chris.
> >
> > We're not... we're using svn+ssh exclusively.
>
> This is trickier. You can log the existence of the connections based
> on the account used, particularly if you use a shared user, and
> especially if you run sshd on a non-standard port with distinct logs.
> So you can do some connection tracking. But svnserve does *NO* logging
> of read operations, so once you have the SSH tunnel established, it's
> a complete black box.
>
> That would actually make a good feature request, and with the new
> commercial sponsors of Subversion, they might be cooperative with such
> a feature request. But I wouldn't expect it in the planned subversion
> 1.7 release.
Received on 2011-04-02 04:10:09 CEST