Re^4: Strange SSH Behavior via system or exec

If this were the case, wouldn't the second case fail as well?

$ perl -e 'system("ssh -l usr remotehost date")’         # works
[download]

Comment on Re^4: Strange SSH Behavior via system or exec Download Code

Replies are listed 'Best First'.
Re^5: Strange SSH Behavior via system or exec by Anonymous Monk on Sep 18, 2014 at 16:40 UTC
As soon as you give system more than one arg, it does not invoke the shell (see also exec), meaning that the arguments such as `"-l usr"` are passed on to `ssh` without interpretation by the shell, usually causing the command to interpret them literally. In your example, there is only one argument to system, so whitespace is interpreted as it would normally be by the shell (more precisely, if there are shell metacharacters, the command is passed to the shell, if there aren't, the command is split on whitespace and executed directly).	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: Strange SSH Behavior via system or exec
by Anonymous Monk on Sep 18, 2014 at 16:40 UTC

As soon as you give system more than one arg, it does not invoke the shell (see also exec), meaning that the arguments such as "-l usr" are passed on to ssh without interpretation by the shell, usually causing the command to interpret them literally.

In your example, there is only one argument to system, so whitespace is interpreted as it would normally be by the shell (more precisely, if there are shell metacharacters, the command is passed to the shell, if there aren't, the command is split on whitespace and executed directly).

[reply]
[d/l]
[select]