Bug 27188

Summary:

fix of rsh non-interactive mode behaviour

Product:

Base System

Reporter:

midom <midom>

Component:

bin

Assignee:

Jonathan Chen <jon>

Status:

Closed FIXED

Severity:

Affects Only Me

Priority:

Normal

Version:

4.3-STABLE

Hardware:

Any

OS:

Any

Attachments:

Description	Flags
file.diff	none

Description midom 2001-05-07 20:40:11 UTC

This issue catched my observations when I had to do some background tasks 
rsh'ing into devices, but doing nothing. That turned to be background task
issue, documented in BUGS, but still, after specifying -n, nothing worked.

Then I tried to do some listing commands in interactive mode, but specifying
-n flag. The command immediately terminated. If I used sleep | rsh, then it worked,
but additional delay was not the solution. Then I tried to fix this problem and here
we have a working fix.

How-To-Repeat: 
rsh -n IP COMMAND

make sure IP is address of really strange device.

Comment 1 ru freebsd_committer

2001-05-14 20:00:01 UTC

Responsible Changed
From-To: gnats-admin->freebsd-bugs

Misfiled PR.

Comment 2 Jonathan Chen freebsd_committer

2002-07-07 17:19:02 UTC

I'm a little hesitant of adding new features to support broken proprietary 
software.  Please let me know if this is still a problem for you, and if 
so, you can also try 'rsh IP command < /dev/null &', which would be another 
workaround that doesn't involve modifying the source code.

-Jon

Comment 3 Jonathan Chen freebsd_committer

2002-07-07 17:20:42 UTC

State Changed
From-To: open->feedback


awaiting user feedback

Comment 4 Jonathan Chen freebsd_committer

2002-07-07 17:20:42 UTC

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


awaiting user feedback

Comment 5 Domas Mituzas 2003-01-11 16:01:19 UTC

Hi,

the method you suggested is one of millions I tried (and afaik is same 
as -n), and that obviously does not work. Anyway, right now I don't have 
to execute any commands on that hardware, but the problem for other 
users still remains :)

I shared my case, it's a software designer's choice whether to bother 
about such proprietary cases.

Cheers,
Domas

Comment 6 Mark Linimon freebsd_committer

2008-01-26 00:28:02 UTC

State Changed
From-To: feedback->closed

Close this one, with bugmeister hat on. 

It's been several years since it came in, and it doesn't seem that 
anyone else has had a similar problem (or at least enough of them to 
make it worth our while to change the software).  Working around 
uncommon hardware is probably best left to local patches.  But thanks 
for the submission.