I chose to explicitly ssh flight@$FlightNode in doit scripts in order to view the log file. Perhaps there is no reason to do that. I think I should embrace the use of .ssh/config and require users to ensure that they can ssh $FlightNode.
Note that in the case where the instrument and GSE are operating without access to DNS, FlightNode must be specified as an IP address rather than a hostname. This is true even if the IP address is associated with the hostname in .ssh/config. Alternately, the IP/hostname mapping can be specified in /etc/hosts (or C:\Windows\System32\drivers\etc\hosts).
If doit is really the only place where I am using ssh flight@$FlightNode, then perhaps I can simply disable ssh login as user flight, which will save that step in the user setup process.
I chose to explicitly
ssh flight@$FlightNodein doit scripts in order to view the log file. Perhaps there is no reason to do that. I think I should embrace the use of .ssh/config and require users to ensure that they canssh $FlightNode.Note that in the case where the instrument and GSE are operating without access to DNS, FlightNode must be specified as an IP address rather than a hostname. This is true even if the IP address is associated with the hostname in .ssh/config. Alternately, the IP/hostname mapping can be specified in /etc/hosts (or C:\Windows\System32\drivers\etc\hosts).
If doit is really the only place where I am using
ssh flight@$FlightNode, then perhaps I can simply disable ssh login as user flight, which will save that step in the user setup process.