From: bert hubert <ahu@ds9a.nl>
To: Michael T Kerrisk <mtk-lists@gmx.net>
Cc: netdev@oss.sgi.com
Subject: Re: Strangeness when write()-ing zero-length datagrams
Date: Mon, 9 Aug 2004 17:40:57 +0200 [thread overview]
Message-ID: <20040809154057.GA30659@outpost.ds9a.nl> (raw)
In-Reply-To: <19357.1092062293@www39.gmx.net>
On Mon, Aug 09, 2004 at 04:38:13PM +0200, Michael T Kerrisk wrote:
> Godday,
>
> On Linux 2.4.26 and 2.6.7, if we connect a datagram socket and
> then use write() to send 0 bytes, a datagram is NOT generated
> (this happens in both the Unix and Internet domains).
> Datagrams are generated in this case for send() and sendto()
> though.
Some postings were made about this some time ago, it appears SUS has an
opinion on zero byte writes:
If nbyte is 0, write() will return 0 and have no other results if the file
is a regular file; otherwise, the results are unspecified.
http://www.opengroup.org/onlinepubs/007908799/xsh/write.html
The send(2) manpage states:
The send() function is identical to sendto() with a null pointer dest_len
argument, and to write() if no flags are used.
Which means that a zero byte send() without flags is unspecified.
Also note that it is hard if impossible to usefully inform userspace of the
reception of a zery byte packet - returning 0 from recvfrom may also mean an
'orderly shutdown'.
Do you actually have a need for zero byte packets?
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-08-09 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 14:38 Strangeness when write()-ing zero-length datagrams Michael T Kerrisk
2004-08-09 15:40 ` bert hubert [this message]
2004-08-09 15:59 ` Michael T Kerrisk
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=20040809154057.GA30659@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=mtk-lists@gmx.net \
--cc=netdev@oss.sgi.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: link
Be 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 NNTP newsgroup(s).