1 | # NOTE: '#' in column 0 is a comment. |
---|
2 | |
---|
3 | local 0 |
---|
4 | localhost 1 - >slave1.out |
---|
5 | localhost 1 - >slave2.out |
---|
6 | |
---|
7 | # lxplus015.cern.ch 1 - >slave1.out |
---|
8 | # lxplus016.cern.ch 1 - >slave2.out |
---|
9 | # xplus017.cern.ch 1 - >slave2.out |
---|
10 | |
---|
11 | # The general format is that "local 0" (required) implies creation of a master. |
---|
12 | # Otherwise there is one line per slave. |
---|
13 | # The first field is the hostname or localhost (in a form valid for "rsh") |
---|
14 | # If you prefer ssh over rsh, then (e.g. in csh): setenv RSH ssh |
---|
15 | # The second field, 1, is obligatory. |
---|
16 | # The third field is an absolute or relative pathname (e.g.: ./XXX or ../XXX) |
---|
17 | # of the binary. A relative pathname is appended to path of the binary |
---|
18 | # on master. The slave process will execute in the same directory |
---|
19 | # as the current working directory of the master, if possible. |
---|
20 | # Otherwise, the slave will execute in the home directory. |
---|
21 | # If the third field is `-', then the command line (including arguments) |
---|
22 | # for that slave will be the same as on the master. |
---|
23 | # Any additional fields (fourth and beyond) are appended to the |
---|
24 | # command line for that slave only. |
---|
25 | # Note that '>slave1.out' works, redirecting standard output. However, |
---|
26 | # the output file, slave1.out, will be placed in the home directory. |
---|
27 | # Currently, `localhost' implies the Bourne shell, and any other |
---|
28 | # name implies the default user shell for that machine. |
---|
29 | # By default, standard output and error are sent to user tty (a la rsh). |
---|
30 | # |
---|
31 | # The format is inherited from MPICH, which grew from P4. |
---|
32 | |
---|
33 | #========================================================================= |
---|
34 | #EXAMPLE: |
---|
35 | # # Master process |
---|
36 | # local 0 |
---|
37 | # # One slave process on local computer, using same binary and same arguments |
---|
38 | # localhost 1 - |
---|
39 | # # One remote slave process, with absolute path to binary and no arguments |
---|
40 | # regulus.ccs.neu.edu 1 /ccs/tmp/gene/a.out |
---|
41 | # # One slave using alpha architecture, |
---|
42 | # # with path of alpha binary relative to binary of this master process. |
---|
43 | # # Output placed in slave-alpha-1.out in user's home directory. |
---|
44 | # alpha.ccs.neu.edu 1 ../alpha/a.out > slave-alpha-1.out |
---|
45 | |
---|
46 | #========================================================================= |
---|
47 | #IF YOU HAVE PROBLEMS: |
---|
48 | # MPINU uses "rsh" to start a slave process. Diagnose it via: |
---|
49 | # rsh REMOTE_SLAVE_HOST hostname |
---|
50 | # If it doesn't work or if it asks you for a password, try: |
---|
51 | # 1. Add a .rhosts file on the remote host and specify your local host. |
---|
52 | # 2. Sometimes adding .localhost to your .rhosts helps. |
---|
53 | # 3. Specify an alternative to "rsh" in your shell. For example: |
---|
54 | # RSH=ssh; export RSH # in Bourne shell, bash, etc. |
---|
55 | # setenv RSH ssh # in csh, tcsh, etc. |
---|
56 | # 4. If you use "ssh", you may also need to copy keys to allow |
---|
57 | # login to the remote host without a password. |
---|
58 | # It's also possible that mpinu guessed badly the hostname of your local host. |
---|
59 | # If you suspect this, on the master try (in csh, tcsh): |
---|
60 | # setenv CALLBACK_HOST LOCAL_MASTER_HOST |
---|
61 | # where LOCAL_MASTER_HOST is the correct hostname of the local master. |
---|
62 | |
---|