On 9/22/06, Daniel <daniel123+svn@gmail.com> wrote:
> Garrett Rooney <rooneg <at> electricjellyfish.net> writes:
> > Well, in that case I'd suggest getting us either a network trace of
> > the problem (via ethereal or something like that) or a neon debug
> > trace (you'll need Subversion 1.4 on the client for windows to do
> > that, it wasn't turned on for previous versions).
> >
> > For getting a neon debug trace, look at the servers config file on
> > your client, specifically the section about neon-debug-mask.
> >
> > -garrett
> >
>
> I checked the server, all the running services.
> It's not running any firewall.
>
> I've found the servers config file and made the adjustment.
>
> However, and this will sound silly, I can't figure out a good way to log the
> results.
>
> Is there a good way to do that?
It writes the output to standard error, so on a Unix machine I'd do
something like svn diff blah blah 2>log.txt, maybe that'll work on a
windows shell (I honestly don't know, don't have a windows box around
right now to try).
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 22 21:49:56 2006