On Sat, Feb 6, 2016 at 4:22 PM, Daniel Shahaf <d...@daniel.shahaf.name> 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 multiple instances in parallel.) >
Thank you! This proved to be good advice. I was unaware I could run multiple svnserve processes in parallel. When I started a second svnserve process, I discovered it worked perfectly fine with my authz setup. Also, I noticed that doing "svn log" was starting to produce a "Network connection closed unexpectedly" error on the client side, making me suspicious my main svnserve process was getting flaky for whatever reason. I restarted my main svnserve process and my problem went away. I don't understand why my svnserve process starting behaving this way, but the problem is resolved for now. I was able to modify my authz file to achieve my current access goals. Many thanks for helping me get unstuck! Best regards, Rick Varney
