Re: Command Executing problem in perl.

Hi,

Just a hint to help yourself:

Print the $cmd string, copy&paste it to your shell and see what happens. Often you see unbalanced "

You have to be careful with output-redirection and using ssh-command. You must be aware of where the output file wil be created, on the remote side or the local side

With the backtick operator you want to grab the output of the script, but as soon as you redirect STDOUT you'll get nothing. So `$cmd` with no assignment is functional more or less equivalent to system($cmd).

Comment on Re: Command Executing problem in perl.

Replies are listed 'Best First'.
Re^2: Command Executing problem in perl. by leslie (Pilgrim) on Jun 27, 2012 at 09:14 UTC
Thanks for ur rply. yeah I have executed in shell. It has displayed the same error. It should create the file in the remote machine, not in local machin. This same script is working in some other machine.	[reply]
Re^3: Command Executing problem in perl. by Anonymous Monk on Jun 27, 2012 at 09:32 UTC
"It should create the file in the remote machine, not in local machine" I'm pretty sure your local shell (the thing executing those strings) doesn't work like that For example this creates the /local/allways on local machine `$ echo > /local/allways` [download] Compare that with this, which only prints stuff to terminal, it creates no files `$ echo "echo > /local/allways"` [download] See Behind the GUI lives the Shell and How Command Line Parameters Are Parsed See also system and Config#sh	[reply] [d/l] [select]