Re: nc - unbuffered input

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--RRgzuVFEVumtByJmvXyOYxKS9zL63ZVr4
Content-Type: multipart/mixed; boundary="OJVJaWKj9ppsHNEzi54ZZEbqCN8yHvmdN";
 protected-headers="v1"
From: Kamil Rytarowski <[email protected]>
To: JP <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Subject: Re: nc - unbuffered input
References: <CAHN8BqrnvKatTk+CmQJM7f2-1cGnXmH5gWzOCoCWjZrSyVXoNw@mail.gmail.com>
 <[email protected]>
 <CAHN8BqpTdqVqc8yYZL07LKPknrCDbSEZVDmLhPJuchc8hSgDsA@mail.gmail.com>
 <CAHN8Bqrh62gKs=aCA-JWUQTjsFR6qx8aB-JwpEafMt8QWtDdrQ@mail.gmail.com>
In-Reply-To: <CAHN8Bqrh62gKs=aCA-JWUQTjsFR6qx8aB-JwpEafMt8QWtDdrQ@mail.gmail.com>

--OJVJaWKj9ppsHNEzi54ZZEbqCN8yHvmdN
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 14.12.2018 03:32, JP wrote:
> Have you had success with STDBUF* ?  I've had success with STDBUF1=3DU
> when set with setenv() from within the c script itself, but haven't
> had any luck at all with STDBUF0=3DU or STDBUF=3DU from the command lin=
e.
>=20
> I tried:
> $ STDBUF=3DU
> $ export STDBUF
> $ nc localhost 65535
>=20

I'm attaching with a debugger to __senvbuf and it's hit and Unbuffered
option set, but after typing some number of characters and new line
characters.

gdb --args nc localhost 65535

It needs proper investigation whether this is the expected behavior.

> JP
> On Thu, Dec 13, 2018 at 2:08 PM JP <[email protected]> wrote:
>>
>> I tried that, it wasn't working for me
>> On Thu, Dec 13, 2018 at 10:27 AM Kamil Rytarowski <[email protected]> wrote:=

>>>
>>> On 13.12.2018 15:04, JP wrote:
>>>> Might there be another soul that desires a netcat with unbuffered in=
put?
>>>>
>>>> usage for unbuffered client mode: nc -B localhost 65535
>>>>
>>>> (I hope the patch comes through ok)
>>>>
>>>
>>> Is it possible to use STDBUF=3DU in env(1) as documented in setbuf(3)=
?
>>>



--OJVJaWKj9ppsHNEzi54ZZEbqCN8yHvmdN--

--RRgzuVFEVumtByJmvXyOYxKS9zL63ZVr4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJABAEBCAAqFiEELaxVpweEzw+lMDwuS7MI6bAudmwFAlwTTqgMHG41NEBnbXgu
Y29tAAoJEEuzCOmwLnZsgogQAJ45Ep7YSKxOwfzdwSmfBl/jy61TWVtlRpQjLa6S
UJLEfIvTnjNs7zDzEzq/VJ8m2sy8Ri0i9MenEqTeiULD+QtO4DGxiQa7IZ/bAp6W
Pz0EWDW6gC+RUISo8Jbv/vd1JiBCANBE5kztjIRTOKX+kvaBMt6FLnEQXl2BmtXm
GVmYMfm1D++gtkD1isL3Mex9wbKLMY5n2CDCeCJ7KaKQiJwpT46FKMJyzZjiXlHs
Ax3OkjNbTJi9D3Yozef/EHMuVLpQ15BWuNfPaVOo/7o7P418bqAQV3dgDnHi02tA
rT+i2n4AXcF8hW2t25wBTxCgDZKv5Zamk2XWQka7mTABzLoTn6UX20wybPJIMv/g
Z7NRez+FQMYB4ARuiDFrfmAqEolZEbqKGbgupX+LraEyITL0mKn4Va/3AZ9YW5JQ
Cphlvoiuqh8WBnWnA5UVWWu2YsSzUyi4S8tOoQqg7TP4kiHlKgrZL9iC/BN2eh3X
bzU3xuw3YWIPabVcTJAxDf2mTWwBl2J41bRBtATEiH+vhMkTsPFQ+Og7JuUuJ2YK
rOpZCC5Y1hE3ff6ee+trszcr9u8cAPShfHR1f8hKlk0kwcgcAWEIoftKgwQZO2nI
iHYek3cxLiCpkzB7PjKrBgyx2r8V2zi3tR9sayM5N7QfvfRfcOR7L4bSQhFtYeoX
GUoI
=nFTa
-----END PGP SIGNATURE-----

--RRgzuVFEVumtByJmvXyOYxKS9zL63ZVr4--