[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: close() behavior when there are multiple fds for a socket
|
From: |
Paul Eggert |
|
Subject: |
Re: close() behavior when there are multiple fds for a socket |
|
Date: |
Thu, 14 Oct 2021 16:09:49 -0700 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.1.0 |
On 10/14/21 16:03, Ben Pfaff wrote:
https://pubs.opengroup.org/onlinepubs/9699919799/
This specification has a lot of cases that explicitly apply only to the
last close of an object, either using that language or by saying that
something happens when "all file descriptors associated with" an
object are closed. But it doesn't say that for sockets.
Yes, and you're right that this is a typo.
(Should I submit a request for clarification to the spec maintainers?)
Sure, and you can do so as described here:
https://www.opengroup.org/austin/
(look for "Defect Reports").
- close() behavior when there are multiple fds for a socket, Ben Pfaff, 2021/10/14
- Re: close() behavior when there are multiple fds for a socket,
Paul Eggert <=
- Re: close() behavior when there are multiple fds for a socket, Ben Pfaff, 2021/10/14
- Re: close() behavior when there are multiple fds for a socket, Paul Eggert, 2021/10/14
- Re: close() behavior when there are multiple fds for a socket, Ben Pfaff, 2021/10/15
- Re: close() behavior when there are multiple fds for a socket, Eric Blake, 2021/10/15
- Re: close() behavior when there are multiple fds for a socket, Ben Pfaff, 2021/10/15
- Re: close() behavior when there are multiple fds for a socket, Bernhard Voelker, 2021/10/21
- Re: close() behavior when there are multiple fds for a socket, Ben Pfaff, 2021/10/21