DIETtestTool man page

DIETTestTool — Example of a tool for DIET using the LogCentral

Name

DIETTestTool - Example of a tool that connects to the LogCentral without any filter and that display all the messages published. It is used as an example for the DIET program. All received published messages are also stored in a log file.

Synopsys

DIETTestTool [options] ...

Description

DIETTestTool connects to the LogCentral and get the messages (by default all, a file containing filters may be passed as an argument). The tool both display and save the messages in a log file. This log file may be given or will be created with a fix name "DIETLogTool.log".

Before starting the LogCentral, you must:

·
launch a CORBA Naming Service.
·
launch log forwarders if needed
·
launch LogCentral service
·
Launch the DIETTestTool
·
Use a component to publish messages

Options

·
The first argument is the destination output file that will contain the displayed logs.
·
The second one is a filter to use in the tool

[Remark: There is no option letter, the order is fixed]

Example

·
Launching the LogCentral
LogCentral -config ./LogCentral.cfg
·
Launching the tool
DIETTestTool
·
Launching the tool to store the logs in the toto.log file
DIETTestTool toto.log
·
Launching the tool to store the logs in the toto.log file with the filter in the filter.txt file
DIETTestTool toto.log filter.txt

Rationale

The LogTool uses CORBA as its communication layer. While it's a flexible and robust middleware, its deployement on heterogeneous networks still is delicate and may require using ssh tunnels.

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), testComponent(1)

Author

haikel.guemar@sysfera.com, kevin.coulomb@sysfera.com

License: GPLv3

Info

2011-05-16 0.1