Date: Sat, 17 Oct 2009 13:58:53 -0400 From: "Mikhail T." <mi+thun@aldan.algebra.com> To: Jilles Tjoelker <jilles@stack.nl> Cc: Kostik Belousov <kostikbel@gmail.com>, stable@freebsd.org Subject: Re: Can close-ing a pipe trigger a SIGPIPE? Message-ID: <4ADA05DD.2080207@aldan.algebra.com> In-Reply-To: <20091017175555.GA76378@stack.nl> References: <4AD9F4ED.2050002@aldan.algebra.com> <20091017172718.GJ2160@deviant.kiev.zoral.com.ua> <4ADA01C2.3000303@aldan.algebra.com> <20091017175555.GA76378@stack.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Jilles Tjoelker ΞΑΠΙΣΑΧ(ΜΑ):
> It seems unwise to assume that a write(2) of 0 bytes is a noop.
> Even if it is, doing it is a waste of a system call.
This is not my code -- it is part of the implementation of Tcl's
"close" command. I'm trying to unravel, where this write coming from,
but, meanwhile, it would be useful to find out, if FreeBSD's handling of
such writes changed recently, wouldn't it?
Because this self-test used to pass cleanly before, so either FreeBSD
changed, or the Tcl did (not the TclX extension, which did not change in
years). Thanks for your help...
-mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ADA05DD.2080207>