comment on

side-note to vinoth.ree: if the powers-to-be running your environment would not allow installing a battle-tested Perl module and turn its authors' free hardwork and dilligence to corporate profit, then they will surely freak out screaming if they see you calling an executable without its extension. Alas they probably have no idea and are just cargo-culting.

Calling executables with no extension it's a feature turned into a huge security hole (attributions to the usual culprit). You call C:/Windows/System32/OpenSSH/scp but which one is it? scp.com, scp.exe, scp.bat, scp.cmd, scp.vbs? PATHEXT will tell you that and who knows who and what messed up with that already. (To be fair, Unix has already this problem with PATH, windows has it with both PATH and PATHEXT)

Anyway, a suggestion for the problem at hand: perhaps create a batch file and insert your commands there and make sure that it runs OK. Then call the batch file from your perl script. If that works, then keep altering your quotes ...

bw, bliako

In reply to Re: scp file from windows10 to unix server by bliako
in thread scp file from windows10 to unix server by vinoth.ree

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks