Opened 10 years ago

Closed 10 years ago

#449 closed help (fixed)

setting up ssh-agent for PUMA

Reported by: lecmtw Owned by: ros
Component: PUMA Keywords: ssh
Cc: Platform:
UM Version:



I'm going through the instructions at to set up the ssh-agent for use with MONSooN.

I've downloaded the setup script as suggested, but have neither a .profile nor .kshrc in my home directory to add the line to. Should I just create one?

Also, when I skip this step and just run the setup script from the command line:

I get:

/home/lecmtw/.ssh/environment.puma: line 1: setenv: command not found
/home/lecmtw/.ssh/environment.puma: line 2: setenv: command not found
Initialising new SSH agent…
/home/lecmtw/.ssh/environment.puma: line 1: setenv: command not found
/home/lecmtw/.ssh/environment.puma: line 2: setenv: command not found

Any help much appreciated!

Change History (4)

comment:1 Changed 10 years ago by ros

  • Keywords ssh added
  • Owner changed from um_support to ros
  • Status changed from new to accepted
  • UM Version <select version> deleted

Dear Matthew,

In answer to your first question: Yes, just create yourself a ~/.profile and add the line . $HOME/.ssh/setup to it.

I'm confused by your setenv problem as my environment.puma file does not contain any references to setenv. Could you change permission on your ~/.ssh directory and the files below to give me read access so that I can take a look and investigate further.


comment:2 Changed 10 years ago by ros

Doh! Sorry the penny has just dropped….. setenv is a bash shell command and is not available in ksh shell.

I'm guessing you changed your shell from the default ksh to bash? Thus your environment.puma file is in bash syntax, but the ~/.ssh/setup runs under bourne/ksh. Try replacing the #!/bin/sh with #!/bin/bash in ~/.ssh/setup.

comment:3 Changed 10 years ago by lecmtw

I think the pennies dropped at the same time! Just had the same thought.
I'd switched the shell to bash many moons ago.

You can tell it's a Friday!!!!

Looks like it is working fabulously now, thanks!


comment:4 Changed 10 years ago by ros

  • Resolution set to fixed
  • Status changed from accepted to closed

Problem resolved. Ticket Closed.

Note: See TracTickets for help on using tickets.