[Bug 544935] Re: netcat-openbsd exits too soon
Several people in this thread have indicated that they have wasted hours if not days to track down seemingly random failures. The Ubuntu manpage guarantees this to work: echo -n "GET / HTTP/1.0\r\n\r\n" | nc host.example.com 80 The original OpenBSD nc does not even have the -q option: http://www.openbsd.org/cgi- bin/man.cgi?query=nc&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html In short, there is no good way to debug the issue quickly, especially if the failures are sporadic (like on localhost). Given that this bug was introduced by Ubuntu, the importance should be raised to "high". -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544935] Re: netcat-openbsd exits too soon
Soren, netcat in the most recent Fedora does not have this behavior. "If you depend on a specific behaviour, you should be specifically asking for said behaviour rather than relying on default values." ISTM that this advice is meant for libvirt. - Seriously, this does not apply when every nc other than Ubuntu nc has the same default. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544935] Re: netcat-openbsd exits too soon
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544935] Re: netcat-openbsd stdout broken on Ubuntu
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.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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
