bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS problem with ssh


From: Paul Eggert
Subject: Re: CVS problem with ssh
Date: Thu, 15 Sep 2005 13:13:45 -0700
User-agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux)

Derek Price <address@hidden> writes:

> Paul, did you ever do anything more than outline this solution?

Yes, I generated this patch:

http://lists.gnu.org/archive/html/bug-cvs/2005-07/msg00034.html

Unfortunately, as I wrote in that email, I can't reproduce the bug
with CVS 1.12.12, so I can't really test that the patch fixes the bug
in general.  Also, Alexander Taler wrote that the patch does not
correct the bug for him.  Please see:

http://lists.gnu.org/archive/html/bug-cvs/2005-07/msg00037.html

I haven't yet had the time to investigate it further.


> I'm not asking you to - I am just getting ready to revisit it and
> thought if you had written any code it might make my job easier.

Thanks.  I'd greatly appreciate it if you could get to the bottom of
the problem.  (If you can reproduce it, that's probably most of the
work right there....)


One more thing.  I am still using CVS_RSH=/home/eggert/bin/ssh4cvs in
my environment, where ssh4cvs is the following script.  Perhaps this
could be put into the CVS FAQ?  Even if we fix the bug for newer
versions of CVS, people will be using old versions for a while.

#! /bin/sh

# Arrange so that ssh's stderr is never stdout,
# by interposing a "cat" process between ssh's
# stderr and our stderr.  Why bother?  Because
# ssh puts stderr into nonblocking mode, and
# CVS (which uses stdio for stdout) gets confused
# if stdout and stderr are the same file.
# See:
# http://lists.gnu.org/archive/html/bug-cvs/2002-08/msg00032.html

exec 3>&1

exit `((ssh "$@" 2>&1 >&3; echo $? >&4) | cat -u >&2) 4>&1`




reply via email to

[Prev in Thread] Current Thread [Next in Thread]