Diff for "ndsproxy"

Differences between revisions 3 and 5 (spanning 2 versions)

The NDS Proxy lets you get DAQ channel data and testpoints from offsite.

The code, scripts, and documentation may be found in target/ndsproxy. The code runs on NODUS. It needs to be restarted by hand when NODUS is rebooted.

Software to use the ndsproxy may be found in Software Tools.

To restart ndsproxy, ssh to nodus, cd to /caltech/target/ndsproxy then run start_ndsproxy.

You can check that its running by doing 'ps -ef | grep nds'. You should get something like this:BR {{{nodus:ndsproxy>ps -ef | grep nds controls 22048 1 0 02:46:38 pts/7 0:00 tclshexe ./ndsproxy -l 8088 -s fb -p 8088 -l 8088 -s fb -p 8088 controls 22092 18588 0 02:49:42 pts/7 0:00 grep nds }}}

-  ⇤ ← Revision 3 as of 2009-08-13 00:30:37 → 
  Size: 444
  Editor: RobertWard
  Comment:
+   ← Revision 5 as of 2011-02-06 10:54:15 → ⇥
  Size: 704
  Editor: RanaAdhikari
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 3:
-The code, scripts, and documentation may be found in target/ndsproxy.

Currently it runs on rana but we're going to move it to [[nodus]].
+The code, scripts, and documentation may be found in target/ndsproxy. The code runs on NODUS. It needs to be restarted by hand when NODUS is rebooted.
-Line 8:
+Line 6:
+----
To restart ndsproxy, ssh to nodus, cd to /caltech/target/ndsproxy then run '''start_ndsproxy'''.
 Line 9:
-The above instructions are iffy.  To restart ndsproxy, ssh to nodus, cd to /caltech/target/ndsproxy then run start_ndsproxy.  All should be well in the world again.
+You can check that its running by doing 'ps -ef | grep nds'. You should get something like this:[[BR]]
{{{nodus:ndsproxy>ps -ef | grep nds
controls 22048     1  0 02:46:38 pts/7    0:00 tclshexe ./ndsproxy -l 8088 -s fb -p 8088 -l 8088 -s fb -p 8088
controls 22092 18588  0 02:49:42 pts/7    0:00 grep nds
}}}