linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Chaloupka <jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH]: unix.7: mentioning SOCK_STREAM socket for ioctl_type of ioctl function
Date: Thu, 14 Aug 2014 15:40:30 +0200	[thread overview]
Message-ID: <53ECBC4E.3070700@redhat.com> (raw)
In-Reply-To: <53CF9457.7070409-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

ping

On 07/23/2014 12:54 PM, Jan Chaloupka wrote:
> From https://bugzilla.redhat.com/show_bug.cgi?id=1110401.
>
> unix.7 is not clear about socket type of ioctl_type argument of ioctl 
> function. The description of SIOCINQ is applicable only for 
> SOCK_STREAM socket. For SOCK_DGRAM, udp(7) man page gives correct 
> description of SIOCINQ.
>
> ---
>  man7/unix.7 | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/man7/unix.7 b/man7/unix.7
> index b0ade5b..6bcc8ba 100644
> --- a/man7/unix.7
> +++ b/man7/unix.7
> @@ -299,7 +299,9 @@ The correct syntax is:
>  can be:
>  .TP
>  .B SIOCINQ
> -Returns the amount of queued unread data in the receive buffer.
> +For
> +.B SOCK_STREAM
> +socket the function returns the amount of queued unread data in the 
> receive buffer.
>  The socket must not be in LISTEN state, otherwise an error
>  .RB ( EINVAL )
>  is returned.
> @@ -319,6 +321,10 @@ defined in
>  .\" That number is normally larger than the number of bytes of pending
>  .\" output. Since this info is, from userland's point of view, 
> imprecise,
>  .\" and it may well change, probably best not to document this now.
> +For
> +.B SOCK_DGRAM
> +socket, see
> +.BR udp (7).
>  .SH ERRORS
>  .TP
>  .B EADDRINUSE
> @@ -450,4 +456,5 @@ see
>  .BR cmsg (3),
>  .BR capabilities (7),
>  .BR credentials (7),
> -.BR socket (7)
> +.BR socket (7),
> +.BR udp (7)

-- 
Jan Chaloupka
------------------------------
* Software Engineer          *
* ENG Base Operating Systems *
* Red Hat Czech, s. r. o.    *
* UTC+1 (CET), jchaloup      *

--
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:[~2014-08-14 13:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 10:54 [PATCH]: unix.7: mentioning SOCK_STREAM socket for ioctl_type of ioctl function Jan Chaloupka
     [not found] ` <53CF9457.7070409-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-08-14 13:40   ` Jan Chaloupka [this message]
2014-09-09  7:05   ` Jan Chaloupka
2014-10-16 10:51   ` Jan Chaloupka
2014-10-17 14:35   ` Michael Kerrisk (man-pages)
     [not found]     ` <54412934.9060602-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-10-18 15:26       ` Jan Chaloupka
  -- strict thread matches above, loose matches on Subject: below --
2014-10-18 15:36 [PATCH] " Jan Chaloupka
     [not found] ` <20141018153600.15536.67496.stgit-/v0jm+aXwyk2pP1PFFXgSPXAX3CI6PSWQQ4Iyu8u01E@public.gmane.org>
2015-02-05  9:51   ` Michael Kerrisk (man-pages)

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=53ECBC4E.3070700@redhat.com \
    --to=jchaloup-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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 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).