From owner-freebsd-current@FreeBSD.ORG  Mon Nov 24 10:06:51 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A764B16A4F8
	for <current@freebsd.org>; Mon, 24 Nov 2003 10:06:51 -0800 (PST)
Received: from smtp.noos.fr (nan-smtp-20.noos.net [212.198.2.120])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BB7DE43F85
	for <current@freebsd.org>; Mon, 24 Nov 2003 10:06:49 -0800 (PST)
	(envelope-from boyd@insultant.net)
Received: (qmail 26147 invoked by uid 0); 24 Nov 2003 18:06:48 -0000
Received: from unknown (HELO coma) ([81.64.132.185])
          (envelope-sender <boyd@insultant.net>)
          by 212.198.2.120 (qmail-ldap-1.03) with SMTP
          for <current@freebsd.org>; 24 Nov 2003 18:06:48 -0000
Message-ID: <03a601c3b2b5$7bc15b80$b9844051@insultant.net>
From: "boyd, rounin" <boyd@insultant.net>
To: <current@freebsd.org>
References: <20031123141408.GA1426@ratsnest.hole>
	<20031124174457.GB27782@madman.celabo.org>
Date: Mon, 24 Nov 2003 19:05:02 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: Re: [PATCH] libc_r bug: successful close(2) sets errno to ENOTTY
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Nov 2003 18:06:51 -0000

From: "Jacques A. Vidrine" <nectar@FreeBSD.org>
> The application is broken.  You must only check errno if you get an
> error indication from the library call.

errno is only meaningful after a syscall error.

it is also well known that stdio uses isatty(3) (or equivelant) that may
set errno to ENOTTY.