This is not a bug, quotes are needed when wildcarding.
As Jim Belonis of the University of Washington reported:
>Quote your remote command properly so the local 'filename globbing'
>doesn't take place.
>e.g.
>rsh REMOTE 'ls *'
>or
>rsh REMOTE ls '*'
>
>
Original Question:
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?
>J.James(Jim)Belonis II, U of Washington Physics Computer Cost Center Manager
>belonis_at_phys.washington.edu Internet University of Washington Physics
Dept.
>http://www.phys.washington.edu/~belonis r. B234 Physics Astronomy Building
>1pm to midnite 7 days (206) 685-8695 Box 351560 Seattle, WA
98195-1560
>
>
Received on Wed Nov 25 1998 - 00:00:41 NZDT