Re: CVS problem with ssh

> If you prefer a different fix that _can be done by us_, that's fine > with me. Just as long as we fix the problem. WE CAN'T FIX THE PROBLEM. Yes we can. The problem that needs to be fixed is a problem in using cvs with ssh in use for communication to the repository. If ssh runs i

Re: CVS problem with ssh

Richard M. Stallman writes: > > If you prefer a different fix that _can be done by us_, that's fine > with me. Just as long as we fix the problem. WE CAN'T FIX THE PROBLEM. Nothing you do to the car can fix the potholes in the road. You can spend all the time and money you want upgrading the s

Re: CVS problem with ssh

Richard M. Stallman wrote: >If the problem occurs with fflush, most likely it will also occur >with fwrite, fclose, etc. fflush is merely the guinea pig here. > >We may have to send bug reports for the systems where it does not always work. > > Agreed. A failed retry in this case is n

Re: CVS problem with ssh

That's essentially *ALL* of them. How many time do I have to say it -- nonblocking mode violates the fundamental assumtions about how files are supposed to behave It didn't convince me the first time, and repeating it won't convince me either. We need to get this bug fixed, and sayin

Re: CVS problem with ssh

Richard M. Stallman writes: > > We may have to send bug reports for the systems where it does not always work. That's essentially *ALL* of them. How many time do I have to say it -- nonblocking mode violates the fundamental assumtions about how files are supposed to behave and virtually *no* cod

Re: CVS problem with ssh

If the problem occurs with fflush, most likely it will also occur with fwrite, fclose, etc. fflush is merely the guinea pig here. We may have to send bug reports for the systems where it does not always work. However, even on those systems, this is change likely to be a big improvement. I

Re: CVS problem with ssh

That's the goal, but we need to iron out some technical difficulties first, as there is an incompatibility with another gnulib module and (more important) it's not yet clear that the proposed approach will actually work. If it works well to solve this problem for CVS, that's good e

Re: CVS problem with ssh

"Richard M. Stallman" <[EMAIL PROTECTED]> writes: > I am not sure what job that program does. The program is too long for > me to read it just to try to figure that out. The program arranges for fflush to have a nontrivial amount of buffered data to flush. It then calls fflush, so the buffer is

Re: CVS problem with ssh

I just checked FreeBSD libc, and it appears that fflush fails once its underlying write fails with EAGAIN. So it appears that this approach won't work under FreeBSD. That's not a good sign. Isn't that a bug in FreeBSD? We can try to work around bugs in various systems, but it is not

Re: CVS problem with ssh

"Richard M. Stallman" <[EMAIL PROTECTED]> writes: > Would you please include this module in gnulib? That's the goal, but we need to iron out some technical difficulties first, as there is an incompatibility with another gnulib module and (more important) it's not yet clear that the proposed appro

Re: CVS problem with ssh

Would you please include this module in gnulib? Please respond to me. ___ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnulib

Re: CVS problem with ssh

I am not sure it is useful to install this in Glibc. Its main use is for application programs that want to be more or less portable, and for that use, gnulib is exactly the right place. ___ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org

Re: CVS problem with ssh

Derek Price <[EMAIL PROTECTED]> writes: >>You have to include stdio.h first, then #undef fwrite, then >>#define fwrite. It can be done (Emacs did it, after all), but I don't >>recommend it. >> > Isn't this the standard behavior for a GNULIB module's header file? > This is almost exactly what unl

Re: CVS problem with ssh

Hi bug-gnulib, I'd like to reopen a discussion on this list from last September: . At the end of that discussion I didn't create the blocking-io module due mostly to Paul Eggert's objections (and a lack of time on my part, espec