Synergy Project Home Page

Home Installation Setup Concepts Programming Compiling Debugging Execution Architecture Conclusions References

 

BUILDING.GIF (11846 bytes)
Setup

Synergy V3.0 runtime environment includes the following four elements:

1) A .sng_hosts file in the user $home directory. This file contains all accessible hosts from the current host. Each line in this file contains host IP address, host name, protocol name, operating system name and login ID. A line with a "#" mask prevents the host from being used for parallel processing.

This is an ASCII file and can be edited manually or through an interface program.

(Since this file defines all useable hosts, in order to maintain a "single system image", the user should copy this file to all other hosts that are not sharing the same file system. )

Example Content:

129.32.32.102 argo.cis.temple.edu tcp unix shi
#129.32.1.100 astro.ocis.temple.edu tcp unix shi
155.247.182.16 spartan.cis.temple.edu tcp unix shi

Click here for a real file for the snowhite cluster.

The following commands can be used to manipulate this file:

Creating new using /etc/hosts:    %shosts [default | ip_addr]
Add a host:                                %addhost host_name [-f]
Delete a host:                            %delhost host_name [-f]
Delete all hosts:                         %dhosts
Choose hosts:                             %chosts

2) A .rhosts file in your root directory. The .rhosts file defines all trusted hosts from the login host. Click here for an example file for the snowhite cluster.

3) An active SNG_PATH symbolic definition pointing to the directory where Synergy V3.0 is installed and an active Synergy command path. This is done by

%source /usr/local/synergy/sng.sh

assuming that /usr/local/synergy is the directory containing the Synergy installation files.

4) Start daemons on selected hosts (defined in ~/.sng_hosts):

%sds.sh

5) To check the status of all remote daemons:

%cds

6) To kill all remote daemons:

%kds.sh

Note: This command only kills the daemons started by your own login. It will NOT kill daemons by others.

 

Copyright @1995-2005 Temple University.
For problems or questions regarding this web contact shi@temple.edu.
Last updated: March 05, 2004.