Source
[...]
From ORBit 0.5.3, IIOP communications over IP sockets are disabled by default for security reasons. You should create an /etc/orbitrc (for a system-wide settings), or an ~/.orbitrc (for one user's setting) containing something like :
ORBIIOPUSock=1 ORBIIOPIPv4=1 ORBIIOPIPv6=0Alternatively, you can also use command line parameters.
Source
[...]
Note: The only problem with this code is that it does not work.
ORBit has a NameService which may be enabled by launching the corresponding
"orbit-name-server" but this name server cannot be resolved with this CORBA_ORB_init call.
One needs to use the name-server IOR string which is displayed upon the name server launch.
The recommended method to use it is to launch it with: "orbit-name-server >/tmp/name-service-ior &".
This will store the IOR string in /tmp/name-service-ior which can then be read with code similar
to the one we studied a little sooner.
GNOME solves this problem quite elegantly with the
gnome_get_name_service api function but this will be explained in this part's last chapter.
Source
[...]
Does ORBit provide a naming service?
Yes. In addition, it is possible to use a third-party naming service, e.g. using the --ORBNamingIOR command line option. The 'Interoperable Naming' specification is not yet supported.