Hi Nic,
Here is the output from 'bpsh -ad ps -ax':
0
---------------------------------------------------------------------
PID TTY STAT TIME COMMAND
2428 ? S 0:00 /usr/bin/lamd -H 192.168.1.1 -P 32863 -n 1 -o 0
2912 ? S 0:00
/usr/src/redhat/BUILD/lam-7.0b17/examples/mandelbrot/slave
2945 ? R 0:00 ps -ax --width 120
1
---------------------------------------------------------------------
PID TTY STAT TIME COMMAND
2429 ? S 0:00 /usr/bin/lamd -H 192.168.1.1 -P 32863 -n 2 -o 0
2913 ? S 0:00
/usr/src/redhat/BUILD/lam-7.0b17/examples/mandelbrot/slave
2946 ? R 0:00 ps -ax --width 120
2
---------------------------------------------------------------------
PID TTY STAT TIME COMMAND
2430 ? S 0:00 /usr/bin/lamd -H 192.168.1.1 -P 32863 -n 3 -o 0
2914 ? S 0:00
/usr/src/redhat/BUILD/lam-7.0b17/examples/mandelbrot/slave
2947 ? R 0:00 ps -ax --width 120
3
---------------------------------------------------------------------
PID TTY STAT TIME COMMAND
2431 ? S 0:00 /usr/bin/lamd -H 192.168.1.1 -P 32863 -n 4 -o 0
2915 ? S 0:00
/usr/src/redhat/BUILD/lam-7.0b17/examples/mandelbrot/slave
2948 ? R 0:00 ps -ax --width 120
So it looks like master and slave both run, but the program never
terminates, and the mandel.out file isn't generated.
Mike
Nicholas Henke wrote:
>What do you get for 'bpsh -ad ps -ax' ?
>
>
>
>>Does this look like a configuration problem or a bug?
>>
>>
>
>Does the program actaully run, or does it just drop off to never-never
>land ?
>
>Nic
>
>
|
