|
Size: 444
Comment:
|
← Revision 6 as of 2012-01-03 23:02:37 ⇥
Size: 717
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| The code, scripts, and documentation may be found in target/ndsproxy. | 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 5: | Line 5: |
| Currently it runs on rana but we're going to move it to [[nodus]]. | 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'''. |
| Line 7: | Line 9: |
| Software to use the ndsproxy may be found in [[Software Tools]]. 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 }}} |
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:
{{{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 }}}