[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
|
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
Hello,
playing around with rsh commands (see topic 9636 in this conference)
we also tested the "-n" option of rsh.
The manual states:
-n Redirects any input for rsh to the /dev/null device.
Use this flag if you are in C shell and run rsh in
the background.
We consider the manual (or the rsh program) has some error because
1st) the command executed on the remote machine gets
NO end of file on its stdin
2nd) the input to rsh is definitly NOT redirected to /dev/null
The proof for 1st: any remote command reading stdin is hanging.
e.g.
$ rsh -n localhost 'while read line; do echo $line; done'
We checked 2nd with lsof: the stdin is still connected to tty
Conclusion: with "-n" flag the rsh process simply
doesn't read its stdin
Question: wouldn't it be better to implement the "-n" flag as stated
in the man page (redirecting stdin to /dev/null) ?
This would give an remote command reading stdin an EOF;
remote commands not reading stdin would not be affected;
and rsh processes spawned from csh/ksh into background wouldn't be
stopped with the message "Stopped (tty input)"
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|