certi-devel
[Top][All Lists]
Advanced

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

RE: [certi-dev] CERTI billard test


From: Gotthard, Petr
Subject: RE: [certi-dev] CERTI billard test
Date: Tue, 19 May 2009 10:32:55 +0200

Hi,
Two comments:

(1) Please check also status of the http proxy variables:
CERTI_HTTP_PROXY and http_proxy
http://www.nongnu.org/certi/certi_doc/User/html/execute.html

(2) I've just realized that some of the documentation was probably not
properly commited to the web space and e.g. the HTTP proxy documentation
isn't accessible.
This page
http://www.nongnu.org/certi/certi_doc/User/html/execute.html
has a link to this page, which seems to be unavailable
http://www.nongnu.org/certi/certi_doc/User/html/certi_HTTP_proxy.html


Petr

-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Martin Spott
Sent: Tuesday, May 19, 2009 9:49 AM
To: address@hidden
Subject: Re: [certi-dev] CERTI billard test

Martin Spott wrote:
> Eric Noulard wrote:

>> RTIA believes that your CERTI_HOST is "http" which is obviously
wrong.
>> Are you sure CERTI_HOST is properly set-up in each terminal?
>> 
>> If you want to setup CERTI env var you may use the "myCERTI.[c]sh"
scripts
> 
> Yup, I knew about these and I'm convinced that I knew what they're
> supposed to do  :-)

Mmmmh, I still get an error when I add "http" as an alias to
"localhost" in the /etc/hosts file. Feels like some general error in
the netwok setup - yet it's strange because every other network
communication works perfectly on this machine and I claim to have a
certain clue about IP networking ....  Ah, wait:

jive: ~> billard -fTest -FTest.fed -n1
CERTI Billard 3.3.3cvs
with TIMESTAMP. If you want without TIMESTAMP add -e option.
RTIA:: RTIA has thrown NetworkError exception.
RTIA:: Reason: Cannot connect port <0> on addr <127.0.0.1> : error
=Connection refused
RTIA:: End execution.
UN Socket(RecevoirUN) : : Connection reset by peer
libRTI: exception: NetworkError (read)
Broken pipe


Port 0 !? Well:

jive: ~> setenv CERTI_TCP_PORT 60400
jive: ~> setenv CERTI_UDP_PORT 60500
(the same for the console window to run RTIG, just to be sure)
jive: ~> billard -fTest -FTest.fed -n1
[identical result]


To me this sounds like the 'billard' test program is a bit uncertain
about its network settings - at least on this machine.

Cheers,
        Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are
!
------------------------------------------------------------------------
--


-- 
CERTI-Devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/certi-devel




reply via email to

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