>Number:         8140
>Category:       bin
>Synopsis:       inetd: error message on portmapper failure could be clearer
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug  3 19:20:00 1999
>Last-Modified:
>Originator:     Bill Sommerfeld
>Organization:
	
>Release:        19990801
>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?"
>Audit-Trail:
>Unformatted: