On Sat, Feb 6, 2016 at 4:22 PM, Daniel Shahaf wrote:
>
>
> You can do 'svnserve --foreground -d --root=/path/to/repos
> --listen-port=3691 --log-file=/dev/stdout' and test against that svnserve
> instance to ensure the log messages are related to a particular client
> action. (You can run multipl
Rick Varney wrote on Fri, Feb 05, 2016 at 09:31:40 -0800:
> Errors I see in my svnserve.log that *may* be related are:
>
> 28207 2016-02-03T18:31:50.113582Z xxx.xx.xx.xxx - - ERR - 0 210002 Network
> connection closed unexpectedly
>
> 28540 2016-02-03T18:50:55.871361Z xxx.xx.xx.xxx - - ERR - 0 10
