On Sat, Aug 07, 2010 at 05:31:24PM +1100, Lutaev D. A. wrote:
> We used parallel-2.0.2 and we have problems with such code:
>
> clear;
>
> hosts = [];
>
> for i = 1:nargin
> hosts = [hosts; argv(){i, 1}];
> end
>
> hosts
>
> sockets = connect(hosts)
>
> x = rand(50, 1000);
>
> send(x, sockets(2, :));
> reval("x = recv(sockets(1, :))", sockets(2, :));
> scloseall(sockets);
>
> Programm stucks when it's trying to send x from sockets(1, :) (master) to
> slave (sockets(2, :)).
As I said, I'm unable to reproduce the problem. Maybe it won't help,
but why don't you send a real session transcript (cut-and-paste from
your terminal running Octave) and indicate exactly the command which
"stucks"? Commands which you only intended to give are of no use to
me. Since I have no notion as yet what the cause of the problem is,
the contents of the variables "host" and "sockets" may be important;
why don't you show it? Of corse you should hide the real hostnames,
but I have to see whether they are different, whether the local
machine is among the servers, and what is the length of the hostnames.
Do you use Octave-3.2.4 and parallel-2.0.2 on _all_ machines?
What you still can do is to check whether the server process and child
process are running before and after the "stucking" command (on each
server machine: ps ax | grep octave and post the output (replacing
hostnames, of corse)).
Olaf
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
