I have two machines: haswell, x2 On x2 I have a folder /data2/backup/xfsdump/x2/ with system_md0_Woche28_L0.gz in it. On haswell I have a folder /data2/backup/xfsdump/x2 with system_md0_Woche29_L0.gz in it. Keep in mind we have the same path on both machines. So something with the interpretation of the wildcard goes wrong! When I start the folowing commond from the x2, I do not see the file with 29 on the haswell. ssh root@haswell ls -1ath /data2/backup/xfsdump/x2/system*; Output is ("not found" in english): ls: Zugriff auf /data2/backup/xfsdump/x2/system_md0_Woche28_L0.gz nicht möglich: Datei oder Verzeichnis nicht gefunden I want to see the listing of /data2/backup/xfsdump/x2/system* on the haswell with the file system_md0_Woche29_L0.gz. But it does not work. Wildcard seems to autocomplete the filename on the local machine instead of the remote machine. So I am sure something goes wrong with the wildcard. I do not know in which part of Linux this is implemented. Kernel? Bash? SSH? I am not sure. Perhaps someone can help.
http://lmgtfy.com/?q=+wildcard+in+a+ssh+command+dows+not+work
It's not a bug, it's a feature! Cool! So quotes around a command changes the way of interpretaion even if there are no quotes necessary - very strange behaviour.
