Bug 20515

Summary:	rsh gives misleading IPv4 and IPv6 connection messages
Product:	Base System	Reporter:	Robert Watson <rwatson>
Component:	bin	Assignee:	Hajimu UMEMOTO <ume>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	5.0-CURRENT
Hardware:	Any
OS:	Any

Description Robert Watson freebsd_committer

2000-08-10 06:00:01 UTC

Misleading try/fail messages result in operator confusion

% rsh localhost
connect to address 127.0.0.1: Connection refused
Trying ::1...
connect to address 127.0.0.1: Connection refused
Trying ::1...
connect to address 127.0.0.1: Connection refused
Trying ::1...

It appears that both IPv4 and IPv6 are tried, and both fail from
connection refused.  However, the messages are different and confusing.
Should probably read:

Trying 127.0.0.1...
connect to address 127.0.0.1: Connection refused
Trying ::1...
connect to address ::1: Connection refused
...

Also, rsh now appears to retry connecting via the same medium
multiple times (6 times, in this case).  I do not believe it used to
do that, satisfying itself with one connection refused on IPv4 before
giving up.

Fix: 

None available.
How-To-Repeat: 
Comment out rsh stuf in inetd.conf
rsh localhost

Comment 1 Sheldon Hearn freebsd_committer

2000-08-10 11:31:27 UTC

Responsible Changed
From-To: freebsd-bugs->ume

Over to an IPv6 maintainer.

Comment 2 Hajimu UMEMOTO freebsd_committer

2000-08-10 18:15:00 UTC

State Changed
From-To: open->closed

I fixed to don't retry via the same medium. (lib/libc/net/rcmd.c 1.29) 
Thank you for your report.