Re: [certi-dev] CERTI setup

[Eric Noulard]

2011/7/19  <address@hidden>:
> Ok, unsetting http_proxy works! billards is now running on my ubuntu
> machine.
>
> Thanks for the info!
>
> I am not sure I understand this, however, should I be setting
> CERTI_HTTP_PROXY to the same as http_proxy?

Nope.

> or do I have to unset http_proxy each time I run a federate.

You have to unset proxy settings for CERTI unless the rtig you use needs
to be reached by a proxy.

When a federate starts it needs to contact an RTIG.
It tries to contact an rtig on the host specified in CERTI_HOST env var.

With CERTI the federate's and the rtig may be run on different hosts,
which is what you want with a distributed simulation runtime :-]

This works for heterogeneous hosts as well (rtig on Linux, federate on Windows
or any other kind of combination).

> What is the "correct" way to deal with proxy
> settings/environment variables?

http_proxy/HTTP_PROXY is a de-facto standard used to specify a proxy
to networked-applications
many applications (wget, curl, etc...) do consult those vars in order
to check whether if a
proxy should be used or not.

CERTI_HTTP_PROXY is a CERTI specific variable.

CERTI consults CERTI_HTTP_PROXY value and if CERTI_HTTP_PROXY is not defined
it tries the usual "http_proxy/HTTP_PROXY".

> something like
>
> export CERTI_HTTP_PROXY=$http_proxy

this is un-necessary CERTI will consult CERTI_HTTP_PROXY and then http_proxy.

export CERTI_HTTP_PROXY=""

enables you to make CERTI avoid to use the proxy setting
while keeping the "http_proxy" setting for other applications.

The set of environment variables used by CERTI (rtig, rtia and
federate apps) are described here:
http://www.nongnu.org/certi/certi_doc/User/html/execute.html

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org