bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] gnubg-multi on Windows, exit code 03


From: Joern Thyssen
Subject: Re: [Bug-gnubg] gnubg-multi on Windows, exit code 03
Date: Fri, 25 Jul 2003 15:45:29 +0000
User-agent: Mutt/1.4.1i

On Fri, Jul 25, 2003 at 05:00:01PM +0200, Holger wrote
> 
> This is the accompanying gnubg output:
> 
> GNU Backgammon 0.13-devel  Copyright 1999, 2000, 2001, 2002, 2003 Gary Wong.
> GNU Backgammon is free software, covered by the GNU General Public License
> version 2, and you are welcome to change it and/or distribute copies of it
> under certain conditions.  Type "show copying" to see the conditions.
> There is absolutely no warranty for GNU Backgammon.  Type "show warranty" 
> for
> details.
> 0.13: incorrect weights version (version gnubg.wd  is required, but these 
> weight
> s are 0,14)
> gnubg.weights: No such file or directory
> WARNING: No neural net weights were found.  GNU Backgammon will create an
> initial random network, but this will be unsuitable for use until training
> is complete.  Please consult the manual for information about training, or
> directions for obtaining a pre-trained network.
> (No game) pu slave localhost
> Host set to SLAVE mode.
>   Will notify availability to localhost (127.0.0.1:80) every 10 secs.
>   Hit ^C to kill pending tasks and return to MASTER mode.
> 
> Available processing units:
>   Id  Type    Status     Queue  Tasks                 Address
>    1  Local   Ready          1  rollout analysis      n/a
> 
> Tasks (todo/prog/done)  Rollouts (rcvd/sent/fail)  Evals 
> (rcvd/sent/fail)  Status
>    0 (   0/   0/   0)     0 (   0/   0/   0)     0 (   0/   0/   0)  N/A
>    0 (   0/   0/   0)     0 (   0/   0/   0)     0 (   0/   0/   0)  N/A
>    0 (   0/   0/   0)     0 (   0/   0/   0)     0 
> (   0/   0/   0)  Waiting for
>    0 (   0/   0/   0)     0 (   0/   0/   0)     0 (   0/   0/   0)  N/A
> 
> 
> Host set back to MASTER mode. 

I'm just guessing here:

Try without notification -- you're probably sending notifications to
port 80 on localhost which is the slave... you should send notifications
to the master. You can also use different ports, i.e., let the master
listen on port 2000 and the slave on port 3000.

Jørn




reply via email to

[Prev in Thread] Current Thread [Next in Thread]