[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Svnserve Logging (Yet again)

From: Eric Gillespie <epg_at_pretzelnet.org>
Date: 2006-07-01 03:07:18 CEST

"Dd Mm" <tmoli42@gmx.net> writes:

> > > + Log error and high level information to stdout/err. This
> > > option would have no effect when svnserve is launched with
> > > --tunnel or --inetd.
> >
> > Since i expect most people who want this uses svnserve under
> > supservise/tcpserver or something similar, you need to log to
> > stderr, not stdout, and it needs to work in --inetd mode.
>
> I guess I don't know how tunneled operation works. From what
> you're saying the stderr is not read, so logging can write to
> it without interfering. Ok, that makes sense.

I'm not sure logging for tunneling makes sense, and i was
certainly not suggesting it.

> So in other words it sounds like we need 4 options for logging
> in svnserve.conf:
> 1) error log file
> 2) info/warning log file

> 3) error log stream (stdout or stderr)
> 4) info/warn log stream (stdout or stderr)

I'm obviously failing to communicate the point here. In inetd
mode, stdout is connected to the client. This is why the option
i want must log to stderr. Write errors, warnings, logs, info,
whatever to stderr, each line tagged appropriately. Maybe we
want a log-level setting to say how much of that you want, i
don't know.

BTW, please wrap your lines at 65 columns in the future.

-- 
Eric Gillespie <*> epg@pretzelnet.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 1 03:08:44 2006

This is an archived mail posted to the Subversion Dev mailing list.