[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: close() behavior when there are multiple fds for a socket
|
From: |
Bernhard Voelker |
|
Subject: |
Re: close() behavior when there are multiple fds for a socket |
|
Date: |
Fri, 22 Oct 2021 00:02:11 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 |
On 10/15/21 20:41, Ben Pfaff wrote:
> On Fri, Oct 15, 2021 at 11:40 AM Eric Blake <eblake@redhat.com> wrote:
>> On Fri, Oct 15, 2021 at 09:10:04AM -0700, Ben Pfaff wrote:
>>> What a bureaucratic organization! The bug report form, once I got a login,
>>> requires one to specify a page number and line number, but it seems that
>>> you can only get the PDF version of the spec that has that information if
>>> you belong to an organization that is a member, so I filled those in with
>>> "?"
>>> and am hoping for the best.
>>
>> That's fine. Adding page numbers after the fact is something that
>> happens rather frequently; and I've done in for your bug in particular
>> just now.
>
> Thanks so much!
Would you mind adding the opengroup bug here for reference?
Thanks & have a nice day,
Berny
- 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/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 <=
- Re: close() behavior when there are multiple fds for a socket, Ben Pfaff, 2021/10/21