-q secs quit after EOF on stdin and delay of secs (-1 to
not quit)
Default value is 0, i.e. as soon as stdin EOF's, it terminates. When
you're using printf, it EOF's before the remote server manages to send
back a response. netcat-traditional happens to default to -1. Each of
-1, 0
Confirmed on Intrepid. nc.traditional is not affected.
It would be _very_ nice to give this bug a high priority. I spent several hours
searching for bugs in Twisted and asyncore.py because I simply did not
expect a broken netcat.
--
netcat-openbsd stdout broken on Ubuntu
https://bugs.launchpad.
Oh, and to contribute to the solution: As a workaround, you can add
alias nc='nc -q 1' to your ~./.bash_aliases to revert to the old
behaviour (but only for your user).
--
netcat-openbsd stdout broken on Ubuntu
https://bugs.launchpad.net/bugs/544935
You received this bug notification because you
Oh come on. They managed to break "nc"? Well done!
--
netcat-openbsd stdout broken on Ubuntu
https://bugs.launchpad.net/bugs/544935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I’ve found out something about this bug:
If you use parameter “-q 0”, netcat won’t print the result. This is a bug.
But if you use something else like “-q 1” or something like that, the output
will be correct.
A Ubuntu specific patch changes the default value of parameter -q to the
“bad” value 0
I can confirm this bug.
This bug affects Lucid and also Karmic (and most likely Jaunty and
Intrepid, because the package version is the same).
** Changed in: netcat-openbsd (Ubuntu)
Status: New => Confirmed
--
netcat-openbsd stdout broken on Ubuntu
https://bugs.launchpad.net/bugs/544935
