phantom(1)

PROGRAM
phantom - starts the phantom daemon on a remote host which is used for distributed processing

SYNTAX

phantom

machine
    Where "machine" is the host that you want the phantom daemon started on

[phantomd_opts]
    Where "phantomd_opts" are the phantomd options that will be passed to phantomd on the remote host when starting the phantom daemon.

[-V]
    Gives the version for phantom

[-U]
    Gives the usage for phantom

[-P]
    Prompts for command line options

[-A [file1]]
    Creates the answer file called phantom.ans or file1

[-a [file1]]
    Uses phantom.ans or file1 as the answer file

DESCRIPTION

The phantom program is used to start a remote daemon, "phantomd", on another host. The phantomd remote daemon is used for distributed processing.

Distributed processing means the ability to specify remote machines on which to execute individual Khoros programs. The capability to do distributed processing is implemented via employment of the remote data transport mechanisms. With distributed processing, one needs a method to execute jobs remotely, as well as a mechanism to transport data back & forth from the remote machine. A remote daemon, "phantomd", is started on the remote machine, takes requests to execute a job, and transports data involved with that job using the remote data transport mechanisms.

The distributed processing capability may be taken advantage of either from the cantata visual language, or from individual command line executions of Khoros programs. However, before distributed processing may be utilized, the KHOROS_HOSTS environment variable must be set properly, and the ".rhosts" or ".rhosts.bk" file must be made available at the top level directory of the account on which you are running Khoros. Also, to enable distributed processing, a Khoros "phantomd" daemon must be started on each machine which is to execute jobs remotely.

The KHOROS_HOSTS environment variable simply specifies a file (by default, ".khoros_hosts") in which all computers which are available for remote data transport are listed.

For more information on data transports and distributed processing see Vol 1, Chapter 1 of the Khoros manual.

REQUIRED ARGUMENTS

machine
    type: string
    desc: the name of the host that you want the phantom daemon started on

OPTIONAL ARGUMENTS

phantomd_opts
    type: string
    desc: Where "phantomd_opts" are the phantomd options that will be passed to phantom on the remote host when starting the phantom daemon. see phantomd(1).

EXAMPLES

The following example shows how start a "phantomd" daemon on the host joesgarage.car.

    % phantom joesgarage.car -timeout 60 -connections 20

the -timeout 60 specifies the daemon sill run for 60 minutes, and the -connections 20 specifies the maximum number of incomming connections on that machine.

This example shows how start "phantomd" daemon on the host poopsie, with a timeout of 10 minutes, a transport type of socket, and disassociate the tty after starting.

    % phantom poopsie -transport socket -timeout 10 -daemon 1

By disassociating the tty after starting, the phantomd will not be associated with a tty. This is used if you are rsh'ing the phantomd command. Note, if you do not disassociate the phantomd from a tty, the rsh will not retuen until the phantomd process quits.

SEE ALSO
intro(1), transport(1), phantomd(1), kcp(1), kexec(1), vgparms(3), vutils(3)

RESTRICTIONS
The "phantomd" daemon currently only works with a data transport type of "socket". Other will be implemented in the future.

COPYRIGHT
Copyright 1992, University of New Mexico. All rights reserved.