Skip to main content
Jump to: navigation, search

Configuration issues

Revision as of 02:34, 5 January 2012 by Dcastl2.cct.lsu.edu (Talk | contribs) (New page: Private/Public Key Decryption Failure * If you encounter a "failed to decrypt ''key_name''" message, it may be due to a disparity between the encryption algorithms that generate the impor...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Private/Public Key Decryption Failure

  • If you encounter a "failed to decrypt key_name" message, it may be due to a disparity between the encryption algorithms that generate the imported and exported keys rather than misconfiguration.
  • Try updating to Jcsh 0.1.44 from Orbit by adding [this link] as a repository.
  • See [user-ptp archives] for more details.
  • Jcsh 0.1.44 will be released automatically with Juno.


Configuration / Setup of SDM

  • Download the SDM from http://www.eclipse.org/downloads/download.php?file=/tools/ptp/updates/indigo/ptp-proxy-5.0.4-201111121445.zip
  • Unzip this and run 'sh BUILD' in proxy/org.eclipse.ptp.macosx.x86_5.0.4.201111121445
  • Get a copy of gfortran from here: http://hpc.sourceforge.net/ then install it in / (as root)
  • Launch Eclipse and create a new Fortran Hello World project.
  • Edit the makefile; change the fortran compiler to /usr/local/bin/gfortran, and remove the -O2 optimization.
  • Compile it by clicking on the hammer.
  • Create an Open MPI resource manager.
  • Create a debug configuration using this project and RM, set the executable, and set number of procs to 1.
  • On the debug tab, select SDM from step 2. Make sure session host is 'localhost'.
  • Launch the debug session.


Loading Remote Environment Variables for a Synchronized Project

  • An environment variable is a named value associated with a terminal session. Values take the form of strings, but numeric values can be stored and manipulated as strings.
  • Environment variables are local; thus, if you change a variable in a terminal session, its changes affect only that terminal session.
  • Environment variables are inherited by child processes. Child processes cannot change environment variables associated with the parent.
  • Some important environment variables:
    • PATH: paths to binary files. If you have installed software in user space, make sure you update your $PATH to include the path to those binaries; then you can call them from anywhere.
    • LD_LIBRARY_PATH: paths to shared libraries. If an application in your $PATH uses shared libraries not within $LD_LIBRARY_PATH, you'll need to set $LD_LIBRARY_PATH to include them. Otherwise you will get an error such as: "libsomething.so: could not find shared library"
  • The command for defining an environment variable is export VAR=VALUE, where VAR is the name of the environment variable and VALUE is the value.
  • After definition, environment variables may be referenced as $VAR, with a dollar sign ($) before the variable name. E.g. echo $VAR following the above definition will print VALUE.
  • E.g.:
    • export GREETING="Hello"
    • export PATH=$PATH:$HOME/bin
  • Environment variables can be set per session on the command line, but are not stored. To store them, one may define them in ~/.bashrc or ~/.profile so that they load on startup (the files ~/.bashrc and ~/.profile contain instructions which execute upon startup of a terminal session).
  • If you change ~/.bashrc or ~/.profile and want to start a new session with its changes, use the command source [filename], as in source ~/.bashrc or source ~/.profile.
  • If you are not using bash, then you will need to change the shell-specific configuration.

Back to the top