Date: Thu, 1 Mar 2007 19:46:53 +0300 From: Anton Yuzhaninov <citrin@citrin.ru> To: Ruslan Ermilov <ru@freebsd.org> Cc: freebsd-net@freebsd.org Subject: Re[2]: is setsockopt SO_NOSIGPIPE work? Message-ID: <1047693239.20070301194653@citrin.ru> In-Reply-To: <20070301152942.GA27336@rambler-co.ru> References: <2110071423.20070301151729@citrin.ru> <20070301152942.GA27336@rambler-co.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a cryptographically signed message in MIME format. ------------D414CF8269B3701 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Thursday, March 1, 2007, 6:29:42 PM, Ruslan Ermilov wrote: RE> On Thu, Mar 01, 2007 at 03:17:29PM +0300, Anton Yuzhaninov wrote: >> Is SO_NOSIGPIPE work? >>=20 >> It try to set on socket option SO_NOSIGPIPE but anyway process >> received sigpipe. >>=20 RE> It works, but only if you use send() instead of write(). RE> Alternatively, you can control the behavior on a per RE> message basis, by passing the MSG_NOSIGNAL in the "flags" RE> argument to the send() call (without having to set a RE> socket option). Thanks, with send() it works fine. I think it should be documented in setsockopt(2). --=20 WBR, Anton Yuzhaninov ------------D414CF8269B3701--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1047693239.20070301194653>