Hi Tim, and thanks for the input, but why do you think the
target machine(s) should be enclosed in single quotes?
Target hosts are not enclosed in single quotes according to
the ssh man page, so I don't see why that should be the case
with PuSSH. Practically speaking, sure it works either way,
with or without quotes around the target machine(s), but I
have never used quotes. Please reply with some reasons as to
why you think this is a bug, otherwise I am inclined to
reject this bug report.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tim, you are correct, target ranges don't work without
quotes when using csh or tcsh, presumably for the reasons
you suggested. I will account for this issue in Usage(): and
release a new version. Thanks for pointing out this issue!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=894981
Hi Tim, and thanks for the input, but why do you think the
target machine(s) should be enclosed in single quotes?
Target hosts are not enclosed in single quotes according to
the ssh man page, so I don't see why that should be the case
with PuSSH. Practically speaking, sure it works either way,
with or without quotes around the target machine(s), but I
have never used quotes. Please reply with some reasons as to
why you think this is a bug, otherwise I am inclined to
reject this bug report.
Logged In: YES
user_id=169213
If I tried the example in the help (adjusted to my names)...
> ./pussh -r node[01-04] uptime
./pussh: No match.
I took this error to mean that the shell (tcsh) was finding the
square brackets and tried to match them to files using
globbing.
> ./pussh -r 'node[01-04]' uptime
OR
> ./pussh -r "node[01-04]" uptime
works for me.
Logged In: YES
user_id=894981
Tim, you are correct, target ranges don't work without
quotes when using csh or tcsh, presumably for the reasons
you suggested. I will account for this issue in Usage(): and
release a new version. Thanks for pointing out this issue!