Hi @tom

So, if you want an interactive shell session, why don't you just run ssh with no commands?

:65457300

When you say several people share the server, they also share the same user?

yes

terdon's solution of creating your own rc file seems like a good solution

just make .tomrc and source that for yourself

@tom So you need to execute 10 different scripts?

@terdon If I'm understanding correctly he just wants to setup his own personalized environment on 10 different machines but can't do that through the correct methods since they share users

That's the kind of thing I am trying to understand: what is it you will be doing here. Are you installing things? Are these repetitive tasks? Why not store the commands in a script on the remote and then excecute that script when you log in? Why try to have sop many things in an "ssh command" construct, and then have an active interactive shell?

@jesse_b But one of the requirements is to end up with an open interactive shell, so for that I would just have a file with my commands, run ssh, source the file, continue with the open shell.

@terdon Maybe I'm misunderstanding but I didn't get that the goal was to end with an interactive shell but that later on when an interactive shell is established it will still have the changes from the previous commands

@jesse_b yes

@terdon yes

@tom think of something like this:

$ cat my_commands
alias c=clear
foo(){
  echo "Hello world!"
}
ls
cd /etc

That's a file named my_commands that you store on the remote server. Then, when you ssh, you just do this:

local $ ssh user@remote
remote $ . my_commands
remote $ do whatever else you want, you have everything set up now

Doing . my_aliases is a good idea.But if I'm allowed to wish more, I don't like putting and managing my_aliases files in several remotes because of source managing issue. I want to put them in my bastion server if I can.

Since you do want an interactive shell, having one extra command (. my_commands) to run doesn't seem like a big deal

@tom what's a bastion server?

like a jump box I think

ah

jump server

Then I would do something like defining a function on the bastion like this:

setup_remote(){
  scp my_commands user@remote
  ssh user@remote
}

Then:

You still end up with a file on the remote, but you only have one file to maintain since it is copied over every time.

In any case, this is the kind of thing that should be mentioned in the question: explain that you want to avoid having multiple files. Explain that you need the setup on the bastion. Explain that you have a bastion.

Oh, this is about unix.stackexchange.com/q/773827/22222

That seems great. Thank you. I will try in like 8 hours (I'm in Tokyo and it's 1AM now, nearly going to sleep....

@tom oh good grief, go, go rest! :)

@jesse_b yeah, something like that, exactly

untested and likely doesn't work but maybe can be tweaked to work lol