40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Sun Feb 24 00:14:28 2013, Manasa, Update, SUS, SUS Summary 
    Reply  Sun Feb 24 17:54:34 2013, rana, Update, SUS, SUS Summary 
       Reply  Tue Jun 25 23:57:30 2013, rana, Update, SUS, NDS2 Status 
          Reply  Wed Jun 26 15:11:08 2013, John Zweizig, Update, SUS, NDS2 Status 
             Reply  Fri Jun 28 17:33:33 2013, John Zweizig, Update, SUS, NDS2 Status 
                Reply  Tue Jul 16 19:16:12 2013, rana, Update, DAQ, NDS2 Status 
Message ID: 8750     Entry time: Tue Jun 25 23:57:30 2013     In reply to: 8154     Reply to this: 8757
Author: rana 
Type: Update 
Category: SUS 
Subject: NDS2 Status 

I've restarted the NDS2 process on Megatron so that we can use it for getting past data and eventually from outside the 40m.

1) from /home/controls/nds2 (which is not a good place for programs to run) I ran nds2-megatron/start-nds2

2) this is just a script that runs the binary from /usr/bin/ and then leaves a log file in ~/nds2/log/

3) I tested with DTT that I could access megatron:31200 and get data that way.

There is a script in usr/bin called nds2_nightly which seems to be the thing we should run by cron to get the channel list to get updated, but I' m not sure. Let's see if we can get an ELOG entry about how this works.

Then we want Jamie to allow some kind of tunneling so that the 40m data can be accessed from outside, etc.

ELOG V3.1.3-