Changes between Version 2 and Version 3 of Pantasks_FAQ

Timestamp:

May 14, 2009, 1:50:00 AM (17 years ago)

Author:

Sebastian Jester

Comment:

woops my emacs function isn't perfect

Pantasks_FAQ

@@ -84 +84 @@
         GPC1                    STR     gpc1/camera.config
  END
- 
+}}} 
 so when you run any script that needs to reference the GPC1 camera it will look 
-}}} * first in the current directory for ./gpc1/camera.config
+ * first in the current directory for ./gpc1/camera.config
  * next in the directory defined by your .ipprc PATH variable (in this case /path/to/my/system/level/ippconfig/gpc1/camera.config)
 
@@ -96 +96 @@
 
  * First, check that you can ssh from the machine on which you are running pantasks to the node without being prompted for a password and without errors reading your shell startup file (.bashrc, .cshrc, .profile, .login and the like):
-{{{
   * Try "ssh myhost"
   * If you're prompted for a password, then you need to set up ssh keys, and/or check your ssh configuration.
-}}} * Second, check that you can start up 'pclient' over an ssh connection. For that to work, you need to run 'psconfig ipp-2.6.1' (or whatever the IPP version is called on your system) in your startup file. 
-{{{
+ * Second, check that you can start up 'pclient' over an ssh connection. For that to work, you need to run 'psconfig ipp-2.6.1' (or whatever the IPP version is called on your system) in your startup file. 
   * Try "ssh myhost pclient". If it works, you can exit pclient with "exit" or "quit".
   * If it doesn't work, you need to check your shell configuration (.cshrc or .bashrc) to ensure the IPP environment is being loaded via psconfig. In .cshrc, just make sure that 'psconfig ipp-2.6.1' is executed. In .bashrc, there's a catch: bash doesn't let you use an alias in the same file that defines it, so you need to expand the 'source'  by hand in .bashrc, thus (this fix will be included in the INSTALL instructions in releases post 2.6.1.): 
+{{{
  if [ -f /IPP/psconfig.csh ]; then
     alias psconfig='source /IPP/psconfig.bash'
@@ -109 +108 @@
     alias psconfig='echo psconfig not available'
  fi
-}}} * If there is a long delay between executing the "ssh" command and the shell appearing, there may be a timeout problem.
-{{{
+}}}
+ * If there is a long delay between executing the "ssh" command and the shell appearing, there may be a timeout problem.
   * Make sure your shell configuration is not too complex.
   * One bash user had the IPP environment being set up in both .bashrc and .cshrc, so that psconfig was being called first when bash started, and then again on starting psconfig (which is a csh script).  This produced a long delay, causing the command to time out in pantasks.
-}}} * Finally, this can also be triggered by the readline bug, whose fix is described below under [wiki:#detrend_resid_imfile.pl_triggers_the_error_message_'Unknown_option:_--erbose' detrend_resid_imfile.pl triggers the error message 'Unknown option: --erbose']
+ * Finally, this can also be triggered by the readline bug, whose fix is described below under [wiki:#detrend_resid_imfile.pl_triggers_the_error_message_'Unknown_option:_--erbose' detrend_resid_imfile.pl triggers the error message 'Unknown option: --erbose']
 
 ==== On startup I get "can't find config file. some functions will be unavailable."  Which config file is missing? ====