blob: 430e9d3442d45e8a6e0cfe999fbd4631c23a272b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
$ID$
This example tests the TAO logging service. It generates SII stubs and
skeletons using the TAO IDL compiler. You can either run the client
and server as seperate processes in the same, or different windows (or
machines), or you may run the "runtests.pl" script which will start
both executables.
By default, the client and server use the Naming Service. The
log_server has its own NamingServer implementation, so it doesn't
require you to start the NamingService before starting the client and
server.
The test demonstrates the functionality of the logging service. The
client program will generate 4 logging messages which will be logged
to the screen. The first message will be in the "verbose_lite"
format. The rest will be fully verbose messages. Successful output is
LM_DEBUG@::log() test (1)
Nov 12 14:20:02.0 1998@lambada-hme0@13670@LM_EMERGENCY@::log() test (2)
Nov 12 14:20:02.0 1998@lambada-hme0@13670@LM_INFO@::logv() test (3)
Nov 12 14:20:02.0 1998@lambada-hme0@13670@LM_EMERGENCY@::log2() test (4)
server: ------
% server [-d]
client: -------
% client [-d]
Options: -------
-d Debug flag. It is an additive flag, so more -d's will increase
the debugging level. Only one flag is necessary to enable the
debugging output from the executables, but the debug level
affects how the utilized TAO methods act (including mysterious
debugging messages).
That's all there is to it. If you desire, feel free to change the
logging priorities, verbosity levels and messages in the client
program but note that the maximum length of the message is 1023
characters.
-Matt Braun mjb2@cs.wustl.edu Thursday, Nov 12'th, 1998
|
