We encountered this bug as we were upgrading our production environment
to Lucid. I'm a little disappointed that this fix won't be applied to
lucid, as our production environment is now going to have to be modified
to work around this bug until the next LTS release, by which point we
will have
I have spent several hours trying to debug a C concurrent server that wasn't
delivering data to netcat clients. Finally I have found this web page, from
which I have understood that my application wasn't bugged at all, it was
netcat... Someone you usually trust :(
Thank you very much for having
This should be fixed in natty now.
chuck
** Changed in: netcat-openbsd (Ubuntu Natty)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/544935
Title:
I'd like us to consider fixing this for Natty. I understand changing it
will break users who have adapted to it, but this wouldn't be the first
time functionality of an application has changed between releases. I do
not, however support the idea of changing functionality in a stable
release, ie
** Tags added: glucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/544935
Title:
netcat-openbsd exits too soon
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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:
I just wasted a full, extremely frustrating working day trying to find
why a complicated script involving in-house software and a tangle of
named pipes and background commands stopped working. Now it's after
midnight, I'm still at work, and I found out it's this. I'm right now
very tempted to give
I was wondering for a few hours why I could not see the data after
piping a request to the server until I found this. I mean there is an
easy workaround, but the tutorials found on the internet are not working
in ubuntu due to this bug. For a newbie this is quite confusing. Would
be better to have
+1 for this as a bug; another issue that I haven't seen mentioned is
this breaks scripts that are written for multiple linux distros, many of
which don't even support the -q flag. using -i 1 is a portable
workaround, but adds a delay that is unwanted.
--
netcat-openbsd exits too soon
Why does Ubuntu constantly have to mess with things that had already
been working and tested before, and then subsequently release them into
the repositories so it can break things for everyone?
This isn't just a problem with their version of netcat. I'm also
talking about pulseaudio, upstart,
I also consider this to be a real bug. It breaks many many tests that I
have. Debian had exactly this bug, and they fixed it.
The good news is that the bug has been fixed in debian..
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502188
It was fixed with a new version of quit-timer.patch
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
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
Hello Soren,
thank you for your explanation.
I am in complete agreement with Stefan; it is a bad idea to change the
default behavior of a defacto-standard utility as a workaround for a bug
in a different (and apparently Linux-only) product, regardless of how
long it's been like that on Ubuntu.
** Summary changed:
- netcat-openbsd stdout broken on Ubuntu
+ netcat-openbsd exits too soon
--
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
I've update the description. Feel free to adjust if you feel I'm
misrepresenting the issue.
** Description changed:
- Binary package hint: netcat-openbsd
+ netcat-openbsd's -q setting defaults to 0. This means that as soon as
+ stdin is closed, it will terminate.
- On Lucid Lynx (Beta 1):
+
16 matches
Mail list logo
