OMNINAMES(8) System Manager's Manual OMNINAMES(8)NAME
omniNames - OmniORB Interoperable Naming Service
SYNOPSIS
omniNames [options] [omniORB-options]
DESCRIPTION
This manual page documents briefly the omniNames command.
omniNames is omniORBs Interoperable Naming Service for CORBA, an implementation of the OMG's COS Naming Service Specification. To make it
easy to use omniNames with corbaname URIs, it starts with the default port of 2809 and an object key of NameService for the root naming
context.
When started for the first time omniNames needs to be told which port it should listen on. This is specified with the -start option. Sub-
sequentley omniNames will always determine its port from the log file which it writes.
When omniNames starts up successfully it writes the stringified object reference for its root context on standard error.
OPTIONS
A summary of options is included below. For a complete description, see the HTML pages included in the omniorb-doc package.
-start [port]
This needs to be used the first time omniNames is run. With no port argument the standard default of 2809 is used.
-logdir directory_name
This specifies the directory where the log/data files are kept. By default /var/lib/omniorb-nameserver/ is used.
-errlog file_name
Where to redirect standard error output.
-ignoreport
Ignore the port specification.
ENVIRONMENT
OMNINAMES_LOGDIR
Alternate way to specify the directory where the log/data files are kept.
OMNINAMES_ITBC
Idle time between checkpoints in seconds. It defaults to 15 minutes.
SEE ALSO omniMapper(8).
The programs are documented fully by the HTML documentation in the omniorb-doc package.
AUTHOR
omniNames was written by Duncan Grisby <duncan@grisby.org>
This manual page was written by Floris Bruynooghe <floris.bruynooghe@gmail.com>, for the Debian project (but may be used by others).
30 Apr 2007 OMNINAMES(8)
Check Out this Related Man Page
TESTCOMPONENT(1)TESTCOMPONENT(1)NAME
testComponent - Example of a component for DIET using the LogCentral
NAME
testComponent - Example of a component that connects to the LogCentral and publish some messages. It is used as an example for the DIET
program.
SYNOPSYS
testComponent
DESCRIPTION
testComponent connects to the LogCentral, publishes some messages and then disconnects.
Before starting the LogCentral, you must:
o launch a CORBA Naming Service.
o launch log forwarders if needed
o launch LogCentral service
o launch a tool to visualize the message sent
o Launch the testComponent
OPTIONS EXAMPLE
o Launching the LogCentral
LogCentral -config ./LogCentral.cfg
o Launching the component
testComponent
RATIONALE
The testComponent uses CORBA as its communication layer. While it's a flexible and robust middleware, its deployement on heterogeneous net-
works still is delicate and may require using ssh tunnels.
LICENSE AND COPYRIGHT
Copyright
(C)2011, GRAAL, INRIA Rhone-Alpes, 46 allee d'Italie, 69364 Lyon cedex 07, France all right reserved <diet-dev@ens-lyon.fr>
License
This program is free software: you can redistribute it and/or mod- ify it under the terms of the GNU General Public License as pub- lished
by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the
hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE. See the GNU General Pub- lic Li- cense for more details. You should have received a copy of the GNU General Public License along
with this program. If not, see <http://www.gnu.org/licenses/>.
AUTHORS
GRAAL INRIA Rhone-Alpes 46 allee d'Italie 69364 Lyon cedex 07, FRANCE Email: <diet-dev@ens-lyon.fr> WWW: http://graal.ens-lyon.fr/DIET
SEE ALSO omniNames(1), logForwarder(1), LogCentral(1), DIETTestTool(1)BUGS AUTHOR
haikel.guemar@sysfera.com, kevin.coulomb@sysfera.com
License: GPLv3
COPYRIGHT
DIET developers
0.1 2011-05-16 TESTCOMPONENT(1)