[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lost process output in pipe between Emacs and CVS
From: |
Stefan Monnier |
Subject: |
Re: Lost process output in pipe between Emacs and CVS |
Date: |
Fri, 09 Aug 2002 04:07:48 -0400 |
> > The problem is that people use cvs 2>&1 with CVS_RSH set to ssh, and
> > expect it to work, and think it is a CVS bug when it fails. Educated
> > users don't have a problem.
>
> Perhaps a quick fix then is to detect that stdio has been set to
> nonblocking and output an error message?
The circumstances under which the problem appears are sufficiently
particular that there are tens of quick fixes available. The question
is how to fix it for real such that neither SSH nor CVS nor PCL-CVS
(in Emacs) need to work around the problem at a functionality or
performance cost.
How do non-glibc systems deal with it ? (I've only seen the
problem reported on glibc systems until now)
It seems legitimate to use stdio on stderr without having to worry about
some application that you have forked and that thus shared your stderr,
so I think the problem is that glibc's stdio does not correctly handle
the case where the file is in non-blocking mode.
Stefan
- Re: Lost process output in pipe between Emacs and CVS,
Stefan Monnier <=