On 14.12.2018 03:32, JP wrote: > Have you had success with STDBUF* ? I've had success with STDBUF1=U > when set with setenv() from within the c script itself, but haven't > had any luck at all with STDBUF0=U or STDBUF=U from the command line. > > I tried: > $ STDBUF=U > $ export STDBUF > $ nc localhost 65535 > 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 <rlntlss83%gmail.com@localhost> wrote: >> >> I tried that, it wasn't working for me >> On Thu, Dec 13, 2018 at 10:27 AM Kamil Rytarowski <n54%gmx.com@localhost> wrote: >>> >>> On 13.12.2018 15:04, JP wrote: >>>> Might there be another soul that desires a netcat with unbuffered input? >>>> >>>> usage for unbuffered client mode: nc -B localhost 65535 >>>> >>>> (I hope the patch comes through ok) >>>> >>> >>> Is it possible to use STDBUF=U in env(1) as documented in setbuf(3)? >>>
Attachment:
signature.asc
Description: OpenPGP digital signature