[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS problem with ssh
From: |
Richard M. Stallman |
Subject: |
Re: CVS problem with ssh |
Date: |
Sat, 25 Jun 2005 09:35:23 -0400 |
The code currently works by making the assumption that network reads
will always return chunks of data small enough to be written to stdout
in a single call to fwrite after a single select on fileno (stdout).
What would make some data too long? The nmemb argument of fwrite is a
size_t, and unless fwrite has a bug, it should handle whatever amount
of data you specify.
I don't see why a large amount of data would cause a failure.
Previous messages claimed that it could, but I think I've refuted that
claim. Is there a flaw in the argument I gave?
- CVS problem with ssh, Richard M. Stallman, 2005/06/22
- Re: CVS problem with ssh, Frank Hemer, 2005/06/22
- Re: CVS problem with ssh, Larry Jones, 2005/06/22
- Re: CVS problem with ssh, Derek Price, 2005/06/22
- Re: CVS problem with ssh, Richard M. Stallman, 2005/06/23
- Re: CVS problem with ssh, Derek Price, 2005/06/23
- Re: CVS problem with ssh, Richard M. Stallman, 2005/06/24
- Re: CVS problem with ssh, Derek Price, 2005/06/24
- Re: CVS problem with ssh,
Richard M. Stallman <=
- Re: CVS problem with ssh, Derek Price, 2005/06/27
- Re: CVS problem with ssh, Richard M. Stallman, 2005/06/28
- Re: CVS problem with ssh, Derek Price, 2005/06/28
- Re: CVS problem with ssh, Richard M. Stallman, 2005/06/29
- Re: CVS problem with ssh, Derek Price, 2005/06/29
- Re: CVS problem with ssh, Derek Price, 2005/06/29