NetBSD Problem Report #8140

Received: (qmail 21193 invoked from network); 4 Aug 1999 02:15:44 -0000
Message-Id: <199908040215.CAA11071@orchard.arlington.ma.us>
Date: Wed, 4 Aug 1999 02:15:36 GMT
From: sommerfeld@orchard.arlington.ma.us (Bill Sommerfeld)
Reply-To: sommerfeld@orchard.arlington.ma.us
To: gnats-bugs@gnats.netbsd.org
Subject: inetd: error message on portmapper failure could be clearer
X-Send-Pr-Version: 3.95

>Number:         8140
>Category:       bin
>Synopsis:       inetd: error message on portmapper failure could be clearer
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 03 19:20:00 +0000 1999
>Closed-Date:    Mon Apr 21 00:52:03 +0000 2003
>Last-Modified:  Mon Apr 21 00:52:03 +0000 2003
>Originator:     Bill Sommerfeld
>Release:        19990801
>Organization:

>Environment:

System: NetBSD orchard.arlington.ma.us 1.4 NetBSD 1.4 (ORCHARDII) #54: Sun May 16 10:05:51 EDT 1999 sommerfeld@orchard.arlington.ma.us:/usr/src/sys/arch/i386/compile/ORCHARDII i386


>Description:
	if there are rpc services listed in inetd.conf but portmap
	isn't running, inetd behaves oddly:
		- it fails to be able to accept connections on the
		  normal tcp services.
		- it logs messages like:

 Aug  3 22:12:03 hammerhead inetd[573]: pmap_set: 100001 1 17 65514: Undefined error: 0

when I see "pmap" I think "Kernel pmap module", not "Sun RPC port
mapper".

>How-To-Repeat:
	uncomment rpc services in inetd.conf
	kill portmap
	restart inetd.
>Fix:
	One or more of the following should help:

	Shorten portmapper register RPC timeout?

	Register using TCP rather than UDP so you die with connection
	refused immediately rather than taking a minute to time out?

	Make error message include the string "is portmap daemon running?"
>Release-Note:
>Audit-Trail:

From: Matthias Drochner <drochner@zel459.zel.kfa-juelich.de>
To: sommerfeld@orchard.arlington.ma.us
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: bin/8140: inetd: error message on portmapper failure could be 
 clearer
Date: Sat, 07 Aug 1999 14:36:02 +0200

 sommerfeld@orchard.arlington.ma.us said:
 > 	if there are rpc services listed in inetd.conf but portmap
 > 	isn't running, inetd behaves oddly:
 > 		- it fails to be able to accept connections on the
 > 		  normal tcp services. 

 Actually, it will accept normal connections after all the timeouts
 due to missing portmap replies are passed.

 > 		- it logs messages like:
 > 
 >  Aug  3 22:12:03 hammerhead inetd[573]: pmap_set: 100001 1 17 65514: Undefined error: 0

 I had a look at this a while ago and found that the whole error handling
 of RPC is not well designed and that it is hard to get useful error
 messages. (RPC functions don't necessarily set errno.)
 To fix the bad behaviour you describe I've resorted to use TCP instead
 of UDP to register services with portmap. So a "connection refused"
 is returned immediately.
 (Since this change (pmap_clnt.c,v 1.13 1999/04/17) is quite serious
 it would be too risky to pull it into the 1.4 release branch.)

 best regards
 Matthias


State-Changed-From-To: open->closed 
State-Changed-By: christos 
State-Changed-When: Sun Apr 20 20:51:23 EDT 2003 
State-Changed-Why:  
this was fixed, and then the whole code was replaced. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.