Did you actually try your second example in a shell script (or at the shell command-line prompt)? If so, were you aware that the part following the pipe symbol ("/bin/others") ends up being a process that executes on your local machine? The "echo something" part is being executed via ssh on host1, the output of that operation is then being fed through a pipe on your local machine, and your own local executable file "/bin/others" is being run to process the output.

If that is your intention, and if you are saying that the perl backtick expression is trying to execute the entire pipeline command on host1 (including the "/bin/others" part), I'd have to ask, how do you know it's happening that way? (A common refrain, seen all too often at PerlMonks: "it doesn't work" is not an adequate description of the problem.)

Try a real example whose results, if successful, would leave no doubt that the stuff between "ssh" and the pipe symbol is being run on the remote machine, and the stuff after the pipe is being run locally. Make sure the example works from the command line, then make sure the perl runtime environment matches your shell environment in the relevant respects (PATH, permissions, etc). E.g. for *n*x style machines:

# create a "special" symlink to your "cut" command:

ln -s `which cut` ~/my_cut

# now, assuming your home directory on host1 is different from your lo
+cal one,
# and you don't have a "my_cut" command in your home directory on host
+1:

o=`ssh host1 tail -1 /etc/passwd | ~/my_cut -d: -f3-5`
echo $o

# now with perl:

perl -e '$_=`ssh host1 tail -1 /etc/passwd | $ENV{HOME}/my_cut -d: -f3
+-5`; print'
[download]

You are right. My example is not enough and I assumed what was happening.
It is however my intention that entire commands run on remote machine but results being shown in the local machine.
I will try others and get back to you on this

Hi convenientstore,

Enclose the command you want to be executed on the remote host in quotes, like this:

my $result = `ssh host1 'echo something | /bin/others'`;
[download]

This way echo something | /bin/others will be run on host1 and the result will end up in $result.

If you want to run any sort of complex (pipeline or other sequential) operation entirely on a remote host, you will probably want to use a module. If, for reasons no one else can fathom, you really don't want to use a module, you'll need to break your complex operations down into simple, single-step-at-a-time commands and waste a lot of time doing a series of backtick operations to slog through the sequence.

Either that, or else you'll simply want to create a script on the remote machine that does everything you want, and run that as a single backtick operation from your local perl script.