Debian Bug report logs - #794217
socketpair: unclear where the SOCK_NONBLOCK and SOCK_CLOEXEC flags go

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Goswin von Brederlow <goswin-v-b@web.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: socketpair: unclear where the SOCK_NONBLOCK and SOCK_CLOEXEC flags go

Date: Fri, 31 Jul 2015 12:41:34 +0200

Package: manpages-dev
Version: 3.74-1
Severity: minor
File: socketpair

Hi,

reading 'man 2 socketpair' it is unclear where the new SOCK_NONBLOCK
and SOCK_CLOEXEC flags go in the function call. One has to read
through "man 2 socket" to discover that the type argument now also
serves as flags.

I recommend making this a bit clearer by changing the Notes from:

       Since   Linux  2.6.27,  socketpair()  supports  the  SOCK_NONBLOCK  and
       SOCK_CLOEXEC flags described in socket(2).

to:

       Since   Linux  2.6.27,  socketpair()  supports  the  SOCK_NONBLOCK  and
       SOCK_CLOEXEC flags in the _type_ argument as described in socket(2).

MfG
	Goswin

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages manpages-dev depends on:
ii  manpages  3.61-1

manpages-dev recommends no packages.

Versions of packages manpages-dev suggests:
ii  man-db [man-browser]  2.6.7.1-1

-- no debconf information

Message #10 received at 794217@bugs.debian.org (full text, mbox, reply):

From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>

To: Goswin von Brederlow <goswin-v-b@web.de>, 794217@bugs.debian.org, control@bugs.debian.org

Cc: mtk.manpages@gmail.com

Subject: Re: Bug#794217: socketpair: unclear where the SOCK_NONBLOCK and SOCK_CLOEXEC flags go

Date: Fri, 07 Aug 2015 11:23:07 +0200

tags 794217 fixed-upstream
thanks

Hello Goswin,

On 07/31/2015 12:41 PM, Goswin von Brederlow wrote:
> Package: manpages-dev
> Version: 3.74-1
> Severity: minor
> File: socketpair
> 
> Hi,
> 
> reading 'man 2 socketpair' it is unclear where the new SOCK_NONBLOCK
> and SOCK_CLOEXEC flags go in the function call. One has to read
> through "man 2 socket" to discover that the type argument now also
> serves as flags.
> 
> I recommend making this a bit clearer by changing the Notes from:
> 
>        Since   Linux  2.6.27,  socketpair()  supports  the  SOCK_NONBLOCK  and
>        SOCK_CLOEXEC flags described in socket(2).
> 
> to:
> 
>        Since   Linux  2.6.27,  socketpair()  supports  the  SOCK_NONBLOCK  and
>        SOCK_CLOEXEC flags in the _type_ argument as described in socket(2).

Thanks for the report. I've changed the upstream page, as you propose.

MfG aus München

Michael


> -- System Information:
> Debian Release: jessie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, armel
> 
> Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> 
> Versions of packages manpages-dev depends on:
> ii  manpages  3.61-1
> 
> manpages-dev recommends no packages.
> 
> Versions of packages manpages-dev suggests:
> ii  man-db [man-browser]  2.6.7.1-1
> 
> -- no debconf information
> 
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

Message #17 received at 794217-done@bugs.debian.org (full text, mbox, reply):

From: "Dr. Tobias Quathamer" <toddy@debian.org>

To: 794217-done@bugs.debian.org

Subject: socketpair is fixed now

Date: Tue, 16 Feb 2016 21:36:00 +0100

[Message part 1 (text/plain, inline)]

Version: 4.04-1

Hi,

this bug has been fixed in Debian, thanks for reporting.

Regards,
Tobias

[signature.asc (application/pgp-signature, attachment)]

Send a report that this bug log contains spam.