From rfg@monkeys.com  Fri Dec 21 21:56:31 2001
Return-Path: <rfg@monkeys.com>
Received: from segfault.monkeys.com (246.dsl6660157.rstatic.surewest.net [66.60.157.246])
	by hub.freebsd.org (Postfix) with ESMTP id 1D38237B416
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 21 Dec 2001 21:56:31 -0800 (PST)
Received: by segfault.monkeys.com (Postfix, from userid 1237)
	id AE4296399; Fri, 21 Dec 2001 21:56:25 -0800 (PST)
Message-Id: <20011222055625.AE4296399@segfault.monkeys.com>
Date: Fri, 21 Dec 2001 21:56:25 -0800 (PST)
From: rfg@monkeys.com
Reply-To: rfg@monkeys.com
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: send(2) sometimes yields ECONNREFUSED, but it's not documented
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         33081
>Category:       docs
>Synopsis:       send(2) sometimes yields ECONNREFUSED, but it's not documented
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Dec 21 22:00:01 PST 2001
>Closed-Date:    Sun Jan 6 17:49:01 PST 2002
>Last-Modified:  Sun Jan 06 17:49:32 PST 2002
>Originator:     Ronald F. Guilmette
>Release:        FreeBSD 4.3-RELEASE i386
>Organization:
Infinite Monkeys & Co.
>Environment:
	FreeBSD 4.3-RELEASE

>Description:
	Using send(2) on a previously connected DGRAM socket, I am getting
	an error result with error set to ECONNREFUSED, but this possible
	result isn't documented on the send(2) man page.

>How-To-Repeat:
	Create a DGRAM socket and connect it to some host/port that
	doesn't have anything bound to that port, and that has nothing
	which will be listening for incoming UDP datagrams on that port.
	Then just use send(2) to try to send a packet to that host/port
	and check errno afterwards.

>Fix:
	Edit the ERRORS section of the send(2) man page to indicate that
	an ECONNREFUSED value in errno is a possible outcome of a call to
	send(2) (and maybe also the other functions described on this page).
>Release-Note:
>Audit-Trail:

From: Peter Pentchev <roam@ringlet.net>
To: rfg@monkeys.com
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: docs/33081: send(2) sometimes yields ECONNREFUSED, but it's not documented
Date: Tue, 25 Dec 2001 20:27:31 +0200

 On Fri, Dec 21, 2001 at 09:56:25PM -0800, rfg@monkeys.com wrote:
 > 
 > >Number:         33081
 > >Category:       docs
 > >Synopsis:       send(2) sometimes yields ECONNREFUSED, but it's not documented
 > >Originator:     Ronald F. Guilmette
 > >Release:        FreeBSD 4.3-RELEASE i386
 > >Organization:
 > Infinite Monkeys & Co.
 > >Environment:
 > 	FreeBSD 4.3-RELEASE
 > 
 > >Description:
 > 	Using send(2) on a previously connected DGRAM socket, I am getting
 > 	an error result with error set to ECONNREFUSED, but this possible
 > 	result isn't documented on the send(2) man page.
 
 I think this was fixed in rev. 1.13, committed on May 20, 2001.
 I might be wrong, but my 4.4-STABLE send(2) manual page has the following
 in the ERRORS section:
 
 [ECONNREFUSED]     The socket received an ICMP destination unreachable
                    message from the last message sent.  This typically
                    means that the receiver is not listening on the remote
                    port.
 
 This was even in 4.4-RELEASE :)
 
 G'luck,
 Peter
 
 -- 
 This sentence would be seven words long if it were six words shorter.
State-Changed-From-To: open->feedback 
State-Changed-By: roam 
State-Changed-When: Tue Dec 25 11:31:03 PST 2001 
State-Changed-Why:  
Are you satisfied with the text from rev. 1.13, quoted in my message 
in the audit-trail? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=33081 
State-Changed-From-To: feedback->closed 
State-Changed-By: roam 
State-Changed-When: Sun Jan 6 17:49:01 PST 2002 
State-Changed-Why:  
Feedback timeout; besides, this is actually corrected in 
latter FreeBSD versions. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=33081 
>Unformatted:
