You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by David Kimdon <da...@kimdon.org> on 2003/12/10 20:30:00 UTC
svnserve deprecated warning breaks xinetd
Hi,
The warnings about deprecated options from svnserve go to stderr which
xinetd passes on to the client. This breaks clients, more discussion
here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=222365
It isn't clear to me the best way to fix this. Maybe we can check to
see if stderr is a tty. Or perhaps send the warning in some format
that won't upset the client. Or perhaps do nothing.
Thoughts?
David
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svnserve deprecated warning breaks xinetd
Posted by Philip Martin <ph...@codematters.co.uk>.
David Kimdon <da...@kimdon.org> writes:
> The warnings about deprecated options from svnserve go to stderr which
> xinetd passes on to the client. This breaks clients, more discussion
> here:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=222365
>
> It isn't clear to me the best way to fix this.
A Unixy solution would be to report the warning to syslog, but that's
not portable.
> Maybe we can check to see if stderr is a tty.
I wonder if it would be possible to detect when stdout and stderr are
the same?
> Or perhaps send the warning in some format that won't upset the
> client.
Or use a wrapper that sends stderr to /var/log?
> Or perhaps do nothing.
Doing nothing sounds good :)
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org