public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "a.herefishyfishies at yahoo dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug manual/1983] socket(s, 1) said to discard sent data Date: Tue, 28 Aug 2012 22:17:00 -0000 [thread overview] Message-ID: <bug-1983-131-l1ciVYdgRt@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-1983-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=1983 herefishy <a.herefishyfishies at yahoo dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a.herefishyfishies at yahoo | |dot com --- Comment #3 from herefishy <a.herefishyfishies at yahoo dot com> 2012-08-28 22:17:09 UTC --- I am not so sure the manual is wrong, especially for a remote socket vs. on on the LAN. Please refer to my bug report, with sample client and server code. By actual test it demonstrates that, at least for data sizes around 4K bytes, data is lost unless the connection is deliberately held open by a sleep(1) before close(socket). This was the case for Linux/CentOS but not Solaris, and was MUCH more prone to happen on a remote host but not as often (very rarely) on the local LAN. http://sourceware.org/bugzilla/show_bug.cgi?id=14500 Examples and statistics are included with the above linked bug report. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next parent reply other threads:[~2012-08-28 22:17 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-1983-131@http.sourceware.org/bugzilla/> 2012-08-28 22:17 ` a.herefishyfishies at yahoo dot com [this message] 2013-10-21 6:48 ` neleai at seznam dot cz 2014-06-30 18:16 ` fweimer at redhat dot com 2005-12-06 11:54 [Bug manual/1983] New: " ceder at ingate dot com 2007-10-16 16:48 ` [Bug manual/1983] " bpeeluk at yahoo dot co dot uk 2007-10-16 16:53 ` bpeeluk at yahoo dot co dot uk
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-1983-131-l1ciVYdgRt@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).