Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL
-DHAVE_CONFIG_H -I. -I../bash -I../bash/include -I../bash/lib -g -O2 -Wall
uname output: Linux goffeg.mtv.corp.google.com 2.6.32-gg298-generic
#gg298-Ubuntu SMP Tue Nov 2 01:28:39 UTC 2010 x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu
Bash Version: 4.1
Patch Level: 5
Release Status: release
Description:
Possible bug? Wildcard characters being evaluated at the wrong time.
Repeat-By:
I enter the following commands and get the following results. I am
intending that the whole string be sent to a remote system where any
wildcard characters would be evaluated. From below, it appears that
my wildcard characters are being evaluated locally in ALL cases. Am
I mis-understanding this concept or is there a problem in bash?
There is a file on my local system named /tmp/wtf.lsR and quite a few
similarly paterned files on the remote system. When I remove the local
file, command execution proceeds as expected/desired.
go...@goffeg bash-4.1 ~/gettowork };-) ssh r...@qchu20 ls -al /tmp/\*.lsR
ls: cannot access /tmp/wtf.lsR: No such file or directory
go...@goffeg bash-4.1 ~/gettowork };-) ssh r...@qchu20 "ls -al /tmp/*.lsR"
ls: cannot access /tmp/wtf.lsR: No such file or directory
go...@goffeg bash-4.1 ~/gettowork };-) ssh r...@qchu20 'ls -al /tmp/*.lsR'
ls: cannot access /tmp/wtf.lsR: No such file or directory
