From setiquest wiki
This script receives a list of components to start from the runsse.sh script. The parameters for each component are defined by environmental variables in the env-vars script. The components are started by an ssh to the appropriate host where the appropriate start up command is executed. The authorized_keys file must be set up in ~/.ssh and the NOPASSWD option must be set in /etc/sudoers so that the ssh does not require a password. Note: An ssh must be issued to each component host prior to running SonATA, so that no user response is required, i.e.
> ssh repos The authenticity of host 'repos (220.127.116.11)' can't be established. RSA key fingerprint is 0f:45:ab:5d:c8:09:53:ee:26:3a:8c:b5:3d:fb:65:18. Are you sure you want to continue connecting (yes/no)? yes
The channelizers, DXs, and the packet utilities must run as root (i.e. sudo ./dx ...) to allow fixed-priority POSIX real-time thread scheduling. In interactive mode, the control components script runs in an xterm that is minimized. All the commands used to start the components are echoed there as well as any failures within the script. In batch mode, this information is written to /tmp/sonata-runsse-controlcomponents. A log file, ~/sonata_archive/templogs/controlcomponents-log-YYYYMMDD-HH:MM.txt, echoes any error/info messages that the components return. If a component fails, it is restarted automatically. The components may be restarted/shutdown from the user interface using "control restart/shutdown componentname".
|← runsse.sh||Index||Backend Server →|