Soren,
thank you for considering the issue. However, I still think this is a
bug:
1) The program is called nc.openbsd and nc on OpenBSD does not
have this behavior.
2) I'm not aware of any other nc that has this behavior. One would also
not ship an echo where -n is the default.
3) Ubuntu's manual page gives the following example. Note that no -q
is specified:
echo -ne "GET / HTTP/1.0\r\n\r\n" | nc www.google.com 80
Point 3), which comes directly from the OpenBSD documentation, makes it
clear that a default of -q 0 was never intended.
I think the priority should be raised to "high" (or equivalent).
Let me expand on my previous posting. I tested a Twisted app on localhost.
Because the network is fast enough, this issue appeared only in about 2% of
all cases. Since I'm not aware of any nc with this default behavior, I assumed
random failures in the server.
I don't think Ubuntu should change the standard behavior of widespread Unix
tools.
--
netcat-openbsd exits too soon
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
