Subject: rsh -p broken (rcmd.c, anyone?)
To: None <>
From: Hubert Feyrer <>
List: tech-net
Date: 10/16/2004 02:12:43

aparently 'rsh -p' doesn't work in 2.0 while it works as expected on 
1.6.x. Running on 2.0 with tcpdump in background, I get:

 	vulab# rsh -p 9999 vulab2
 	02:09:54.132547 vulab2vulab.881 > vulab2.3879: S 3878241974:3878241974(0) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 0 0> (DF)

The point in giving it a port number is to really use that (I have a rshd 
running on port 9999 on the target machine for some special stuff).

Is anyone familiar with src/lib/libc/net to comment on why rcmd_af() 
discards the port number, and maybe how to fix the code?

  - Hubert

P.S.: All "use ssh" comments will go to /dev/null.
       I use rsh for a reason.

If wishes were wings,  o"   )~  would fly.            -- Go!