All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Sutin,
	Brian M HS" <Brian.Sutin-ErF4HNK4sl3QT0dZR+AlfA@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: write(2) man page missing error code
Date: Sun, 29 Aug 2010 15:52:45 +0200	[thread overview]
Message-ID: <AANLkTi=Qqd5BBMjuXbxqOPJ0ZYv9LE3ckuiCF3ne0uHq@mail.gmail.com> (raw)
In-Reply-To: <E2C0377E93FA8B4194658987E40226F001073EDC-JC38xCScHSXe46enX5xh1IkgB36zAFJh@public.gmane.org>

Hello Brian,

On Thu, Aug 26, 2010 at 10:30 PM, Sutin, Brian M            HS
<Brian.Sutin-ErF4HNK4sl3QT0dZR+AlfA@public.gmane.org> wrote:
> Manpages-dev 3.23-1
> Linux 2.6.32-24
> Ubuntu Lucid
>
> I am getting the error code EDESTADDRREQ from a write() to a udp port.  It isn't mentioned in the man page as a possibility.

Thanks for the report. For upstream man-pages-3.26, I added the following

--- a/man2/write.2
+++ b/man2/write.2
@@ -128,6 +128,11 @@ so a portable application should check for both
possibilities.
 .I fd
 is not a valid file descriptor or is not open for writing.
 .TP
+.B EDESTADDRREQ
+.I fd
+refers to a datagram socket for which a peer address has not been set using
+.BR connect (2).
+.TP
 .B EFAULT
 .I buf
 is outside your accessible address space.


Cheers,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface" http://blog.man7.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2010-08-29 13:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-26 20:30 write(2) man page missing error code Sutin, Brian M            HS
     [not found] ` <E2C0377E93FA8B4194658987E40226F001073EDC-JC38xCScHSXe46enX5xh1IkgB36zAFJh@public.gmane.org>
2010-08-29 13:52   ` Michael Kerrisk [this message]

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='AANLkTi=Qqd5BBMjuXbxqOPJ0ZYv9LE3ckuiCF3ne0uHq@mail.gmail.com' \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=Brian.Sutin-ErF4HNK4sl3QT0dZR+AlfA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.