In message
Adrian Chadd wrote:
> On 21 July 2013 19:02, Ronald F. Guilmette wrote:
>
>> It has been some time now since I filed my PR but I think that the bottom
>> line is that you need to look at the code (of nc) to understand how it is
>> reacting to EOF on stdin.
>
>Gah, I was kinda hoping
On 21 July 2013 19:02, Ronald F. Guilmette wrote:
> It has been some time now since I filed my PR but I think that the bottom
> line is that you need to look at the code (of nc) to understand how it is
> reacting to EOF on stdin.
Gah, I was kinda hoping not to look at nc, and just work with som
In message
=?ISO-8859-1?Q?Fernando_Apestegu=EDa?= wrote:
>Yes, that is what I tested. Behavior before (truncated output) and after
>(correct output) applying the patch.
OK, good. Thanks.
>If this is going to be the final version of the patch, i.e. if it is going
>to include the -q flag, then
In message
Adrian Chadd wrote:
>Wait a second. What's going on under the hood?
>
>You _should_ be able to shutdown the write side of the socket and have
>it not affect reading.
It has been some time now since I filed my PR but I think that the bottom
line is that you need to look at the code (
In message <20130721041338.2121.qm...@f5-external.bushwire.net>,
"Mark Delany" wrote:
>> servers running certain protocols. For example, the rules of the SMTP
>> protocol... just to name one... require that a client wait until the
>> server has sent out an initial greeting banner before the cl
On Sun, Jul 21, 2013 at 5:05 AM, Ronald F. Guilmette
wrote:
>
> In message z1a3pgbtchaehmbqb5fwpx-7emgbtsj7ay...@mail.gmail.com>
> =?ISO-8859-1?Q?Fernando_Apestegu=EDa?=
> wrote:
>
> >It seems to work for me:
>
> Good.
>
> Just to make sure that we are clear, you are simply confirming what my
>
6 matches
Mail list logo