Re: Secure copy (scp) issue

This is the line from the logfile produced by the -v option:

debug1: Sending command: scp -v -f
Outbound/UBDailyRPT*.TXTUBDAILYRpt_20130817.TXT

(No line break, just email "helping").

There is supposed to be a space following RPT*.TXT - but it is crammed
together. I am wondering about that -f. I don't see that as an
option in the Linux version. The unexpanded command is:

scp -v ${PEDID}@${SERV}:${PATHE}$1 ${PATHO}

First question that has just hit me: Where did that -f come from? My
first impression is that the guy who wrote this isn't even using the
script file. But, if that were the case, how does it connect to the
proper server? First time I had noticed the -f in the debug. I am
also puzzled as to where the 20130817 came from. Perhaps I have been
"persuing a wild fowl".

John McKee

On Wed, Aug 14, 2013 at 1:16 PM, Clay B Carley <cbc@xxxxxxxxx> wrote:

Ah, so to put this more blatantly:

scp -v ${PEDID}@${SERV}:${PATHE}$1 ${PATHO}
Won't work if
scp -v blah@blah:path-is->=-variablename+whitespace-between-names?

For instance, if ${PATHE}$1 is greater than 13 or 14 characters, then it
becomes an issue? But if it's shorter, then it should work OK?

Not that I'm having an issue, but trying to see what the issue could be.

Clay Carley
Sonic.net/ Sonic Telecom

On 08/14/2013 11:07 AM, Scott Mildenberger wrote:

What Chris is saying could make sense if one or more of the parameters are now bigger than they were previously. You may need to add more spaces.

Scott Mildenberger
Programmer/Analyst
Davis Transport Inc.
Missoula, MT
406-728-5510 x128

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Wednesday, August 14, 2013 11:52 AM
To: Midrange Systems Technical Discussion
Subject: Re: Secure copy (scp) issue

Original script had one space between the two parameters. Nothing was truncated. The single space between scp and the first parameter was left alone, but the space between the parameters was totally removed.
Replacing the single space with 4 spaces had the same result - single space following scp and no space between the two parameters. Also, nothing truncated or mangled.

John McKee

On Wed, Aug 14, 2013 at 11:56 AM, Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx> wrote:

I have run into something similar to this before. The problem being that the shell parser would build the command, expanding the variables. It would not insert white space between the parameters so you had to put enough spaces in the line to hold the expanded variables. Try adding a few more blanks in your script and see if the expanded variables still generate the line all run together.

--
Chris Bipes
Director of Information Services
CrossCheck, Inc.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.