Shell Programming and Scripting

I want to cd as well, but the path is not being passed from local to remote. I cant manually cd , this is part of a pipeline, so the cd has to be part of a variable based shell-script.
Any variable for that matter, is there a way to pass variables?

--- Post updated at 10:59 AM ---

Sorry about the confusion, I tried every combination without any luck,

Code:

workdirlocal="/My/Intended/Path/"
sshpass -p password ssh userid@serverB.xxx.org << ENDSSH
workdirremote=\$workdirlocal
cd $workdirremote
echo $(pwd)
ENDSSH

As explained, try the other way round. And, set the -x (--xtrace) option on the remote so you can see what happens.

If i get that right:

You have a server onto which you want to log on using a certain user. If you connect from host A you want the user, after logging in, to go to one certain directory, if you connect from host B you want to go to another directory and so on. Is that right?

If so: there are several options you have. First you could use the output of who -a to find out from where you have connected. A sample output will look similar to:

Code:

bakunin@host $ who -a
           system boot  2019-03-20 15:29
           run-level 3  2019-03-20 15:29
LOGIN      tty1         2019-03-20 15:29              7581 id=tty1
bakunin + pts/0        2019-03-21 16:01   .          8762 (10.1.1.1)

Using this information you can create a script like this to change to the respective directory:

Code:

icomefrom=$(who -a | sed -n '/bakunin/ {;s/.*(//;s/)$//p;}')

case "$icomefrom" in
     10.1.1.1)
          cd /dir/A
          ;;

     10.1.1.2)
          cd /dir/B
          ;;

     .....
esac

Notice that you may also have a variable "SSH_CONNECTION" set which holds essentially the same information.

Another possibility would be to use different users to connect to the host so you can have different login scripts which put you into different directories. All these users might at the end switch their effective UID (via su) so that you end up with always the same user but in different directories.

There will be a myriad of other possibilites, but as long as you do not explain what you (in the grand scheme of things) want to achieve it is hard to find out which one of them is feasible and which one isn't. So tell us about your plans and we will be better able to help you.

I hope this helps.

bakunin

When I set up pipeline processes using ssh, I always use ssh without passwords by just exchanging public and private key pairs... (a one time setup, but saves a lot of time and effort afterwards)


In fact, even when I login for normal work, I mostly use password-less ssh with crypto keys. It is faster, more secure, and easier to set up pipelines of ssh commands.

shouldn't it be this way:

Code:

workdirremote='/My/Intended/Path/'
sshpass -p password ssh userid@serverB.xxx.org << ENDSSH
cd ${workdirremote}
echo $(pwd)
ENDSSH

Thanks a lot for your responses, ${workdir1} seems to do the trick !

Not quite. The echoed value shown in red above is also from the local shell; not the shell running on serverB.xxx.org. And, in Bourne based shells, the current working directory is stored in the variable named PWD, not the variable named pwd (and they are distinct variables because the shell is case-sensitive).

You probably want to replace that line in your script with either:

Code:

echo \$PWD

or:

Code:

pwd

and, if you're having any doubts about which variables are being expanded where, I would suggest using the 2nd form.