Re: [PATCH] socket.7: be explicit that connect(2) respects SO_*TIMEO

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Alejandro Colomar <alx.manpages@xxxxxxxxx>
Subject: Re: [PATCH] socket.7: be explicit that connect(2) respects SO_*TIMEO
From: Luis Javier Merino <ninjalj@xxxxxxxxx>
Date: Sat, 10 Dec 2022 00:51:09 +0100
Cc: Tycho Andersen <tycho@tycho.pizza>, Alejandro Colomar <alx@xxxxxxxxxx>, Michael Kerrisk <mtk.manpages@xxxxxxxxx>, linux-man@xxxxxxxxxxxxxxx
In-reply-to: <a796c0f9-a4bf-bc5d-3953-9c725b53d10e@gmail.com>
References: <20221128205837.2408050-1-tycho@tycho.pizza> <a796c0f9-a4bf-bc5d-3953-9c725b53d10e@gmail.com>

Note that accept(2) is also affected by SO_RCVTIMEO, at least on Linux.

See:

https://stackoverflow.com/questions/5968121/does-so-rcvtimeo-affect-accept

Follow-Ups:
- Re: [PATCH] socket.7: be explicit that connect(2) respects SO_*TIMEO
  - From: Alejandro Colomar

References:
- [PATCH] socket.7: be explicit that connect(2) respects SO_*TIMEO
  - From: Tycho Andersen
- Re: [PATCH] socket.7: be explicit that connect(2) respects SO_*TIMEO
  - From: Alejandro Colomar

Prev by Date: Re: words (and commands) that I learnt because of Branden (was: preferred /proc/<pid>/xxx style?)
Next by Date: Re: Conflicting alias for some man pages
Previous by thread: Re: [PATCH] socket.7: be explicit that connect(2) respects SO_*TIMEO
Next by thread: Re: [PATCH] socket.7: be explicit that connect(2) respects SO_*TIMEO
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Documentation] [Netdev] [Linux Ethernet Bridging] [Linux Wireless] [Kernel Newbies] [Security] [Linux for Hams] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux RAID] [Linux Admin] [Samba]

Powered by Linux