When 'ls' is used with the 'rsh' command it doesn't seem
to work properly. It seems to first check the local
system and then reissue the command to the remote
system for all the files it found locally. It's hard
to explain, but here's the example:
LOCAL system has the following file:
-rw-r--r-- 1 root system 0 Nov 24 15:34 /file1
REMOTE system has the folling files:
-rw-r--r-- 1 root system 9 Nov 24 15:34 /file1
-rw-r--r-- 1 root system 9 Nov 24 15:34 /file2
-rw-r--r-- 1 root system 9 Nov 24 15:35 /file3
When logged onto LOCAL...
LOCAL> rsh REMOTE ls -l file*
-rw-r--r-- 1 root system 9 Nov 24 15:34 file1
NOTICE that it doesn't return 'file2' & 'file3'!!!!
If I create a 'file2' on LOCAL, it will find 'file1' & 'file2'
on REMOTE, but not 'file3'. BUT, if I DELETE 'file1' on LOCAL,
it will return all three files on REMOTE.
Is this the expected behavior of 'rsh' when using the 'ls'
command or is this a bug?
Thanks,
Bob Berrigan
Kent School District
berrigan_at_kent.wednet.edu
Received on Tue Nov 24 1998 - 23:45:26 NZDT