Remotely Conecting an IWS for Command

A new function to connect yourself to the ECS, without the SOC, has been
implemented.
 
To use this functionality;

 1. create a file with the name <iws machine>.<instrument>
         where <iws machine> is the name of the computer you want to connect.
         This name must match what the ECS has in its /etc/hosts file.
                  
         where <instrument> is the name of the instrument.
         It will be one of; CDS, GOLF, LASCO, MDI, SUMER, SWAN, VIRGO, UVCS.

         Example filenames are is; uvcs5.UVCS, cds09.CDS, mdisas.MDI and lasco5.LASCO

   NOTE: The content of the file is ignored, it can be anything.
       It is best to make the files small, i.e. 1 byte, so they transfer quickly.

2. transfer this file to the soc and put it in the 'connectcmd' directory.
   You use the same technique as when sending delayed command or
   background queue files.

Within 3 minutes you should get a connection from the ECS.

NOTE: This function works even when we do not have NRT commanding
available, but when you accept the connection you will NOT get a command
authority token and will NOT be able to command. Your socket will stay open
in the pending condition and may time out, especially if you have a stateful
firewall. The resulting condition may require human assistance in the SOC to
correct. PLEASE, make sure of your commanding times and only connect during
them.


remote_commanding.txt, Written by Chris Dullnig 06 July 2010