diff options
| author | Johnny Willemsen <jwillemsen@remedy.nl> | 2011-10-05 13:58:05 +0000 |
|---|---|---|
| committer | Johnny Willemsen <jwillemsen@remedy.nl> | 2011-10-05 13:58:05 +0000 |
| commit | a2e974b036a5e8957f140b9243f506c6f8aeb12a (patch) | |
| tree | e6d53d55e8e1a6d3d0368497a70e7ad608b2119e /TAO | |
| parent | 3656e04a81035bf736a4dd094957886822a2b696 (diff) | |
| download | ATCD-a2e974b036a5e8957f140b9243f506c6f8aeb12a.tar.gz | |
Fixed fuzz
Diffstat (limited to 'TAO')
34 files changed, 145 insertions, 137 deletions
diff --git a/TAO/orbsvcs/Logging_Service/Basic_Logging_Service/README b/TAO/orbsvcs/Logging_Service/Basic_Logging_Service/README index 5288ca240e1..70cb854f11c 100644 --- a/TAO/orbsvcs/Logging_Service/Basic_Logging_Service/README +++ b/TAO/orbsvcs/Logging_Service/Basic_Logging_Service/README @@ -1,5 +1,7 @@ +$Id$ + The service is registered with the naming service with the name -"BasicLogFactory" . +"BasicLogFactory" . To run the Basic Logging Service: ------------------------ diff --git a/TAO/orbsvcs/Logging_Service/Event_Logging_Service/README b/TAO/orbsvcs/Logging_Service/Event_Logging_Service/README index 4977a7bac72..415127ddbfd 100644 --- a/TAO/orbsvcs/Logging_Service/Event_Logging_Service/README +++ b/TAO/orbsvcs/Logging_Service/Event_Logging_Service/README @@ -1,5 +1,7 @@ +$Id$ + The service is registered with the naming service with the name -"EventLogFactory" . +"EventLogFactory" . To run the Event Logging Service: ------------------------ diff --git a/TAO/orbsvcs/Logging_Service/Notify_Logging_Service/README b/TAO/orbsvcs/Logging_Service/Notify_Logging_Service/README index 282768d11e9..d185cca92e0 100644 --- a/TAO/orbsvcs/Logging_Service/Notify_Logging_Service/README +++ b/TAO/orbsvcs/Logging_Service/Notify_Logging_Service/README @@ -1,5 +1,7 @@ +$Id$ + The service is registered with the naming service with the name -"NotifyLogFactory" . +"NotifyLogFactory" . To run the Notify Logging Service: ------------------------ diff --git a/TAO/orbsvcs/Logging_Service/README b/TAO/orbsvcs/Logging_Service/README index e3bcce3a3f8..9c502e53aaa 100644 --- a/TAO/orbsvcs/Logging_Service/README +++ b/TAO/orbsvcs/Logging_Service/README @@ -1,4 +1,4 @@ -// README v 1.3 dhanvey <d.hanvey@qub.ac.uk> 14:43 30/05/02 +$Id$ Telecom Log Service ------------------- @@ -20,7 +20,7 @@ The Logging Service is comprised of 3 separate services ... There is also a RTEvent Logging Service available ... -4. The RTEvent Logging Service +4. The RTEvent Logging Service $TAO_ROOT/orbsvcs/orbsvcs/Logging_Service/RTEvent_Logging_Service Please see the README documents in each of the above folders for diff --git a/TAO/orbsvcs/Logging_Service/RTEvent_Logging_Service/README b/TAO/orbsvcs/Logging_Service/RTEvent_Logging_Service/README index 9f49da0c078..ff438e480e2 100644 --- a/TAO/orbsvcs/Logging_Service/RTEvent_Logging_Service/README +++ b/TAO/orbsvcs/Logging_Service/RTEvent_Logging_Service/README @@ -1,5 +1,7 @@ +$Id$ + The service is registered with the naming service with the name -"RTEventLogFactory" . +"RTEventLogFactory" . To run the RTEvent Logging Service: ------------------------ diff --git a/TAO/orbsvcs/Naming_Service/README b/TAO/orbsvcs/Naming_Service/README index 9cc96f8575d..c6f84e5ddf6 100644 --- a/TAO/orbsvcs/Naming_Service/README +++ b/TAO/orbsvcs/Naming_Service/README @@ -1,4 +1,4 @@ -// README,v 1.19 2001/02/02 20:21:38 schmidt Exp +$Id$ This directory contains files that implement a server for the TAO Naming Service. In addition, it contains files that run the TAO @@ -81,21 +81,21 @@ The following describes how to run the TAO Naming Service. timing out and throwing a 'Cannot proceed' exception to the client. If no value is set this will never occur. - -d + -d Provides Naming Service specific debug information. By default - no diagnostics are given. + no diagnostics are given. -u directory Use a flat-file persistence implementation that stores object - reference information in a file per context. Each context file + reference information in a file per context. Each context file is placed in the directory specified. - + -r directory Use redundant flat-file persistnece; same as the -u option, except more than one instance of the TAO Naming Service server - can run, each using the same set of disk files, to achieve a - degree of fault tolerence (as long as directory is accessible - to both servers). + can run, each using the same set of disk files, to achieve a + degree of fault tolerence (as long as directory is accessible + to both servers). 3. Environment Variables diff --git a/TAO/orbsvcs/Time_Service/README b/TAO/orbsvcs/Time_Service/README index 2ca9f457b45..0acd0f1f722 100644 --- a/TAO/orbsvcs/Time_Service/README +++ b/TAO/orbsvcs/Time_Service/README @@ -1,4 +1,4 @@ -$Id $ +$Id$ ============================ TAO Time Service============================== @@ -8,7 +8,7 @@ client. The Time Service interface has been implemented as two servants: the clerk and the server. Clients who wish to use the service talk to clerks and the clerks in turn keep their time synchronized globally. The clerks do this by talking to the servers running on -different machines. +different machines. There needs to be at least one time server running in the network. The Clerks update their time periodically from the servers. The servers and clerks @@ -73,12 +73,12 @@ more elaborate distributed time synchronization algorithm. Version Updates : (10th March, 1999) ----------------- -The TAO Time Service has been updated to include the timezone information -in the Universal Time Object. This object now also has an inaccuracy estimate -in it. The inaccuracy is a measure of the skew in the synchronization of +The TAO Time Service has been updated to include the timezone information +in the Universal Time Object. This object now also has an inaccuracy estimate +in it. The inaccuracy is a measure of the skew in the synchronization of the clerks time. It is the difference between the highest and the lowest times -from the servers that the clerk synchronizes its time with. The high-inaccuracy -and the low-inaccuracy fields are also being calculated from the inaccuracy as +from the servers that the clerk synchronizes its time with. The high-inaccuracy +and the low-inaccuracy fields are also being calculated from the inaccuracy as follows : Inaccuracy 64-bits diff --git a/TAO/orbsvcs/orbsvcs/AV/README b/TAO/orbsvcs/orbsvcs/AV/README index e3482716a80..62959f92f2f 100644 --- a/TAO/orbsvcs/orbsvcs/AV/README +++ b/TAO/orbsvcs/orbsvcs/AV/README @@ -1,4 +1,4 @@ -// $Id$ +$Id$ TAO Audio/Video Streaming service --------------------------------- @@ -11,7 +11,7 @@ interfaces for controlling multimedia streams. This directory contains the following files AVStreams_i.{h,cpp}: Implementation of the A/V handshake specification, as well - as base classes for the various interfaces defined in the spec. + as base classes for the various interfaces defined in the spec. Endpoint_Strategy.{h,cpp}: Implementation of various multimedia endpoint activation strategies. diff --git a/TAO/orbsvcs/orbsvcs/Notify/README b/TAO/orbsvcs/orbsvcs/Notify/README index c30991c4c95..66e8f899f6b 100644 --- a/TAO/orbsvcs/orbsvcs/Notify/README +++ b/TAO/orbsvcs/orbsvcs/Notify/README @@ -1,4 +1,4 @@ -README,v 1.5 2000/12/07 05:56:27 pradeep Exp +$Id$ README for the Notification Service ----------------------------------- @@ -31,7 +31,7 @@ another we can deploy dispatching threads using this option. -SourceThreads Deploys a thread pool after event receipt from the supplier. All subsequent notification channel processing can happen on this thread and the original -publishing push() can be ended. Separates server side processing of the +publishing push() can be ended. Separates server side processing of the event from the supplier's publication. diff --git a/TAO/orbsvcs/orbsvcs/PortableGroup/README b/TAO/orbsvcs/orbsvcs/PortableGroup/README index 7faf4cd6e46..9e1bb9f038c 100644 --- a/TAO/orbsvcs/orbsvcs/PortableGroup/README +++ b/TAO/orbsvcs/orbsvcs/PortableGroup/README @@ -12,7 +12,7 @@ For examples on how to use MIOP, see $TAO_ROOT/orbsvcs/tests/Miop. Compilation Note: The PortableGroup library requires the CosNaming library due to references -to it in the IDL from the MIOP specification. It is not really used in +to it in the IDL from the MIOP specification. It is not really used in actual implementation. Implementation Notes: @@ -26,14 +26,14 @@ to the final MIOP specification. The following are current limitations: 2. Disassociating a group reference from a servant is not implemented. If interested in fixing this, be aware of the race conditions if a - servant disassociates during an upcall. The TAO event services all + servant disassociates during an upcall. The TAO event services all have code to handle this issue. 3. Clients must call _unchecked_narrow to narrow any group references since a multicast group manager isn't supported yet (and UIPMC does not support twoway invocations) - 4. TAO does not have a multicast group manager, so groups must be + 4. TAO does not have a multicast group manager, so groups must be assigned by creating a MIOP CORBALOC formatted reference. See the tests or the MIOP specification for example group references. diff --git a/TAO/orbsvcs/tests/Bug_2316_Regression/README b/TAO/orbsvcs/tests/Bug_2316_Regression/README index 89f1c090651..d9767c986bb 100644 --- a/TAO/orbsvcs/tests/Bug_2316_Regression/README +++ b/TAO/orbsvcs/tests/Bug_2316_Regression/README @@ -1,9 +1,9 @@ $Id$ -This client and server in this test both load the UIPMC protocol plug in +This client and server in this test both load the UIPMC protocol plug in (see svc.conf). -The client creates a MIOP object ref and tests that it can be marshalled +The client creates a MIOP object ref and tests that it can be marshalled and demarshalled without problems by passing it over the wire to the server. _Expected successful result_: diff --git a/TAO/orbsvcs/tests/Bug_3444_Regression/README b/TAO/orbsvcs/tests/Bug_3444_Regression/README index f6bd279783d..8041002f925 100644 --- a/TAO/orbsvcs/tests/Bug_3444_Regression/README +++ b/TAO/orbsvcs/tests/Bug_3444_Regression/README @@ -7,7 +7,7 @@ _Expected successful result_: $>run_test.pl Starting IIOP test - server -o /home/vzykov/devel/PrismTech/zbuild/tao161_XXXTAO_gcc423_ipv6-x86_64/tao161/prism/tests/tao690_regression/server.ior + server -o /home/vzykov/devel/PrismTech/zbuild/tao161_XXXTAO_gcc423_ipv6-x86_64/tao161/prism/tests/tao690_regression/server.ior client -k file:///home/vzykov/devel/PrismTech/zbuild/tao161_XXXTAO_gcc423_ipv6-x86_64/tao161/prism/tests/tao690_regression/server.ior -ORBIPHopLimit 1 -ORBDebugLevel 1 -ORBLogFile /home/vzykov/devel/PrismTech/zbuild/tao161_XXXTAO_gcc423_ipv6-x86_64/tao161/prism/tests/tao690_regression/test.log Client's log: TAO (22932|140355161454320) Default_Resource_Factory - codeset manager=0x61b7e0 diff --git a/TAO/orbsvcs/tests/Event/Basic/README b/TAO/orbsvcs/tests/Event/Basic/README index 26408823b69..941b09931b4 100644 --- a/TAO/orbsvcs/tests/Event/Basic/README +++ b/TAO/orbsvcs/tests/Event/Basic/README @@ -1,9 +1,9 @@ -# $Id$ +$Id$ Basic tests for the real-time event channel. This directory contains several tests to exercise the real-time event -channel features, debug it and stress test it. The tests are as simple +channel features, debug it and stress test it. The tests are as simple as possible, but not simpler. Here are some canonical test configurations: diff --git a/TAO/orbsvcs/tests/Event/Mcast/Complex/README b/TAO/orbsvcs/tests/Event/Mcast/Complex/README index e0000644dc7..2648cadd5cc 100644 --- a/TAO/orbsvcs/tests/Event/Mcast/Complex/README +++ b/TAO/orbsvcs/tests/Event/Mcast/Complex/README @@ -1,10 +1,10 @@ -// $Id$ +$Id$ Goals: ------ This is a step up from the Simple mcast test. There are still two Event Channels participating: one sends out its events via multicast, -while the second one listens for events on multicast. +while the second one listens for events on multicast. But this test uses ECG_Mcast_Gateway configured with Complex Address Server and Complex Mcast Handler components. In other words, @@ -21,7 +21,7 @@ configured to use a different mcast group for each event type. Supplier pushes 100 events of each of the three event types to its Event Channel while the consumer waits for events from its EC. Once the consumer receives 100 events of each of the three types it -expects, it destroys its EC and exits. +expects, it destroys its EC and exits. Command-line Options: --------------------- @@ -30,9 +30,9 @@ Consumer: $consumer -ORBInitRef Event_Service=<ior> Supplier: $supplier -ORBInitRef Event_Service=<ior> Mcast-equipped EC: $gateway_ec -ORBsvcconf <conf_file> -i <ior_file> -where +where <ior_file> is the name of the file to which the ior of the Event - Channel will be printed + Channel will be printed <conf_file> is a service conf file used to configure the Event Channel and the multicast components. See consumer-ec.conf or supplier-ec.conf for examples, or @@ -41,14 +41,14 @@ where To run: ------- -Automagically (runs all executables, processes output): +Automagically (runs all executables, processes output): $ run_test.pl Manually: $gateway-ec -ORBsvcconf consumer-ec.conf -i consumer-ec.ior -$consumer -ORBInitRef Event_Service=file://consumer-ec.ior +$consumer -ORBInitRef Event_Service=file://consumer-ec.ior $gateway-ec -ORBsvcconf supplier-ec.conf -i supplier-ec.ior -$supplier -ORBInitRef Event_Service=file://supplier-ec.ior +$supplier -ORBInitRef Event_Service=file://supplier-ec.ior diff --git a/TAO/orbsvcs/tests/Event/Mcast/Simple/README b/TAO/orbsvcs/tests/Event/Mcast/Simple/README index 14c87028fb3..35722d36e2f 100644 --- a/TAO/orbsvcs/tests/Event/Mcast/Simple/README +++ b/TAO/orbsvcs/tests/Event/Mcast/Simple/README @@ -1,16 +1,16 @@ -// $Id$ +$Id$ Goals: ------ This is the most basic test for federating Event Channels via multicast or udp. Two Event Channels participate: one sends out its events via multicast (or udp), while the second one listens for events on -multicast (or udp). +multicast (or udp). -This test can be run with two different configurations: multicast is used +This test can be run with two different configurations: multicast is used for federating event channels in one and udp is used in another. The test uses ECG_Mcast_Gateway configured with Simple Address Server and -Simple Mcast Handler or UDP Handler components. +Simple Mcast Handler or UDP Handler components. Description: ------------ @@ -28,9 +28,9 @@ Consumer: $consumer -ORBInitRef Event_Service=<ior> Supplier: $supplier -ORBInitRef Event_Service=<ior> Mcast-equipped EC: $gateway_ec -ORBsvcconf <conf_file> -i <ior_file> -where +where <ior_file> is the name of the file to which the ior of the Event - Channel will be printed + Channel will be printed <conf_file> is a service conf file used to configure the Event Channel and the multicast components. See consumer-ec.conf or supplier-ec.conf for examples, or @@ -39,24 +39,24 @@ where To run: ------- -Automagically (runs all executables, processes output): +Automagically (runs all executables, processes output): $ run_test.pl Manually: - + Multicast Federation test $gateway-ec -ORBsvcconf consumer-ec.conf -i consumer-ec.ior -$consumer -ORBInitRef Event_Service=file://consumer-ec.ior +$consumer -ORBInitRef Event_Service=file://consumer-ec.ior $gateway-ec -ORBsvcconf supplier-ec.conf -i supplier-ec.ior -$supplier -ORBInitRef Event_Service=file://supplier-ec.ior +$supplier -ORBInitRef Event_Service=file://supplier-ec.ior UDP Federation test $gateway-ec -ORBsvcconf udp-consumer-ec.conf -i consumer-ec.ior -$consumer -ORBInitRef Event_Service=file://consumer-ec.ior +$consumer -ORBInitRef Event_Service=file://consumer-ec.ior $gateway-ec -ORBsvcconf udp-supplier-ec.conf -i supplier-ec.ior -$supplier -ORBInitRef Event_Service=file://supplier-ec.ior +$supplier -ORBInitRef Event_Service=file://supplier-ec.ior diff --git a/TAO/orbsvcs/tests/Event/UDP/README b/TAO/orbsvcs/tests/Event/UDP/README index 55aad804e20..0c99de8bdca 100644 --- a/TAO/orbsvcs/tests/Event/UDP/README +++ b/TAO/orbsvcs/tests/Event/UDP/README @@ -1,4 +1,4 @@ -# $Id$ +$Id$ This directory contains a very simple example of a multicast-based federation of event services. @@ -18,7 +18,7 @@ $ MCast If you need to set the multicast group and port you can use the -m option: -$ MCast -m 224.100.2.1:12345 +$ MCast -m 224.100.2.1:12345 Run the test in multiple machines on the same network. If there is only one process you should only receive 1000 events in the diff --git a/TAO/orbsvcs/tests/IOR_MCast/README b/TAO/orbsvcs/tests/IOR_MCast/README index c1ba4a88b3a..24c68f7b043 100644 --- a/TAO/orbsvcs/tests/IOR_MCast/README +++ b/TAO/orbsvcs/tests/IOR_MCast/README @@ -1,9 +1,9 @@ -// $Id$ +$Id$ This is a simple test for testing the multicast ior parser with format mcast://multicast_address:port:nicaddress:ttl -The Client requests for the IOR of a service that is multicasted. +The Client requests for the IOR of a service that is multicasted. The Server helps get this ior with the use of the TAO_IOR_Multicast class in the libTAO_Svc_Utils library. diff --git a/TAO/orbsvcs/tests/InterfaceRepo/Application_Test/README b/TAO/orbsvcs/tests/InterfaceRepo/Application_Test/README index 113da0997f8..ccaf67f4cae 100644 --- a/TAO/orbsvcs/tests/InterfaceRepo/Application_Test/README +++ b/TAO/orbsvcs/tests/InterfaceRepo/Application_Test/README @@ -40,15 +40,15 @@ The order of events is as follows: through the Naming Service, but here the IOR is read from the file where it was stored by the server. - + (c) The client then makes several calls to the - repository, first searching for an object + repository, first searching for an object with the name 'warehouse'. Once this is found, the client checks to see if 'warehouse' may contain other objects. If so, it gets a list of all the objects 'contained' by warehouse which are interfaces. Each inteface's - name is checked to find one called 'inventory'. + name is checked to find one called 'inventory'. Then the client gets a list of all inventory's operations. Each of these is checked to find one called 'getCDinfo'. The client then gets @@ -60,7 +60,7 @@ The order of events is as follows: sets its return type and adds parameters according to the information extracted from the operation repository object. Notice that - the client does not have the correct string for + the client does not have the correct string for the album title, but one that is commonly used by people when referring to that album. The server will try to be smart about this, and @@ -84,7 +84,7 @@ object to get its InterfaceDef from the respository, and then query the IntefaceDef object to get information about its operations and their parameters. If the command line option -n is passed to the client (or to the Perl script), the client will -resolve the repository by a call to +resolve the repository by a call to orb->resolve_initial_references ("InterfaceRepository") and use information it has (through some unspecified means) about the local name of the interface and of its containing module, @@ -103,9 +103,9 @@ included in the application (in test_i.h) and TAO_IFR_Client added to the list of linked libraries. This will force the static Initializer function in the library to initialize all the IFR typecodes and to load the library. Applications that don't need to call _get_interface -don't need to link this library and can thus keep the server-side +don't need to link this library and can thus keep the server-side footprint smaller. -More information about the Interface Repository can be found in +More information about the Interface Repository can be found in TAO/docs/releasenotes/index.html. diff --git a/TAO/orbsvcs/tests/InterfaceRepo/IDL3_Test/README b/TAO/orbsvcs/tests/InterfaceRepo/IDL3_Test/README index 98b048231ad..2acbcb5d2a0 100644 --- a/TAO/orbsvcs/tests/InterfaceRepo/IDL3_Test/README +++ b/TAO/orbsvcs/tests/InterfaceRepo/IDL3_Test/README @@ -1,7 +1,7 @@ $Id$ This test specializes in the Interface Repository support of -valuetypes and the IDL extensions that were added to +valuetypes and the IDL extensions that were added to support the CORBA Component Model (CCM). Testing of most of the other IDL types can be found in the nearby IFR_Test directory. @@ -25,7 +25,7 @@ and sequence lengths found in test.idl, appear at the top of idl3_client.cpp. This allows the test to be easily extended to cover more complicated use cases. -More information about the Interface Repository can be found in +More information about the Interface Repository can be found in TAO/docs/releasenotes/index.html. diff --git a/TAO/orbsvcs/tests/InterfaceRepo/IDL_Test/README b/TAO/orbsvcs/tests/InterfaceRepo/IDL_Test/README index ec7af78e229..c3e7be4ef93 100644 --- a/TAO/orbsvcs/tests/InterfaceRepo/IDL_Test/README +++ b/TAO/orbsvcs/tests/InterfaceRepo/IDL_Test/README @@ -1,3 +1,5 @@ +$Id$ + This directory runs the IFR compiler on the various IDL compiler stress tests found in $TAO_ROOT/tests/IDL_Test. It will automatically pick up new IDL files as they are added. @@ -30,7 +32,7 @@ The testing goes in three phases: skip the IDL file if the IDL file is known to fail in #1 tao_ifr on the IDL file } - + For each IDL file { skip the IDL file if the IDL file is known to fail in #1 tao_ifr on the IDL file to remove from the IFR diff --git a/TAO/orbsvcs/tests/InterfaceRepo/IFR_Inheritance_Test/README b/TAO/orbsvcs/tests/InterfaceRepo/IFR_Inheritance_Test/README index 5948342f0c9..a1a79808f00 100644 --- a/TAO/orbsvcs/tests/InterfaceRepo/IFR_Inheritance_Test/README +++ b/TAO/orbsvcs/tests/InterfaceRepo/IFR_Inheritance_Test/README @@ -25,8 +25,8 @@ problem and providing non-automated test code. To build this test, the TAO library, the TypeCodeFactory library, the Interface Repository (the last two found in -TAO/orbsvcs/IFR_Service), and these test files must all be built. -In addition, the Interface Repository requires the TAO_Svc_Utils +TAO/orbsvcs/IFR_Service), and these test files must all be built. +In addition, the Interface Repository requires the TAO_Svc_Utils library in TAO/orbsvcs/orbsvcs. To run this test, either use the Perl script run_test.pl, or @@ -34,7 +34,7 @@ To run this test, either use the Perl script run_test.pl, or (Windows) -start the Interface Repository by typing +start the Interface Repository by typing ..\..\..\IFR_Service\IFR_Service @@ -50,7 +50,7 @@ and then IFR_Inheritance_Test -ORBInitRef InterfaceRepository=file://if_repo.ior (Unix) -in this directory, type +in this directory, type ../../../IFR_Service/IFR_Service & @@ -68,8 +68,8 @@ and use the default multicast address for the InterfaceRepository. ../../../IFR_Service/IFR_Service -m 1 -and +and - ./IFR_Inheritance_Test + ./IFR_Inheritance_Test - Scott Harris <harris_s@ociweb.com>
\ No newline at end of file diff --git a/TAO/orbsvcs/tests/InterfaceRepo/IFR_Test/README b/TAO/orbsvcs/tests/InterfaceRepo/IFR_Test/README index 45898fd7299..2b806522ab3 100644 --- a/TAO/orbsvcs/tests/InterfaceRepo/IFR_Test/README +++ b/TAO/orbsvcs/tests/InterfaceRepo/IFR_Test/README @@ -22,8 +22,8 @@ struct_test(), union_test() and exception_test(). To build this test, the TAO library, the TypeCodeFactory library, the Interface Repository (the last two found in -TAO/orbsvcs/IFR_Service), and these test files must all be built. -In addition, the Interface Repository requires the TAO_Svc_Utils +TAO/orbsvcs/IFR_Service), and these test files must all be built. +In addition, the Interface Repository requires the TAO_Svc_Utils library in TAO/orbsvcs/orbsvcs. To run this test, either use the Perl script run_test.pl, or @@ -31,7 +31,7 @@ To run this test, either use the Perl script run_test.pl, or (Windows) -start the Interface Repository by typing +start the Interface Repository by typing ..\..\..\IFR_Service\IFR_Service @@ -40,7 +40,7 @@ in one window, then (in another window) IFR_Test -ORBInitRef InterfaceRepository=file://if_repo.ior (Unix) -in this directory, type +in this directory, type ../../../IFR_Service/IFR_Service & @@ -55,12 +55,12 @@ and use the default multicast address for the InterfaceRepository. ../../../IFR_Service/IFR_Service -m 1 -and +and ./IFR_Test You may add any of the options below to the IFR_Test command line. Both the -Perl script and the test executable have the same command line options. +Perl script and the test executable have the same command line options. They are: -d Outputs the results of queries along with a string @@ -107,7 +107,7 @@ The IFR server is started in this test with locking enabled. Even though the test itself is single-threaded, using this option will ensure that future modifications to IFR code don't cause deadlocks. -More information about the Interface Repository can be found in +More information about the Interface Repository can be found in TAO/docs/releasenotes.index.html. -Jeff Parsons <parsons@cs.wustl.edu>
\ No newline at end of file diff --git a/TAO/orbsvcs/tests/InterfaceRepo/Persistence_Test/README b/TAO/orbsvcs/tests/InterfaceRepo/Persistence_Test/README index 7eae42fd67c..25e136a5665 100644 --- a/TAO/orbsvcs/tests/InterfaceRepo/Persistence_Test/README +++ b/TAO/orbsvcs/tests/InterfaceRepo/Persistence_Test/README @@ -8,8 +8,8 @@ two functions: populate() and query(). To build this test, the TAO library, the TypeCodeFactory library, the Interface Repository (the last two found in -TAO/orbsvcs/IFR_Service), must be previously built. In addition, -the Interface Repository requires the TAO_Svc_Utils library in +TAO/orbsvcs/IFR_Service), must be previously built. In addition, +the Interface Repository requires the TAO_Svc_Utils library in TAO/orbsvcs/orbsvcs. It is far easier to run the test with the provided Perl script @@ -20,7 +20,7 @@ run_test.pl, but to do it by hand, first start the IFR with Then execute the test code with -Persistence_Test +Persistence_Test This will populate the IFR with a few IFR objects. After the test finishes, stop the IFR. Then start it again @@ -43,7 +43,7 @@ The query run of the test code will also destroy all IFR objects that were created - the repository will be left empty except for the primitive kinds which are always there (and cannot be destroyed). -If for some reason IP multicast is not available or enabled on your platform, +If for some reason IP multicast is not available or enabled on your platform, then add -ORBInitRef InterfaceRepository=file://if_repo.ior @@ -63,7 +63,7 @@ destroy() call(s) at the end of the function were not exectuted. Before running the test again, the Interface Repository process should be stopped and restarted to avoid a BAD_PARAM exception. -More information about the Interface Repository can be found in +More information about the Interface Repository can be found in TAO/docs/releasenotes.index.html. -Jeff Parsons <parsons@cs.wustl.edu>
\ No newline at end of file diff --git a/TAO/orbsvcs/tests/Miop/McastHello/README b/TAO/orbsvcs/tests/Miop/McastHello/README index 2b7205b555d..e0657566917 100644 --- a/TAO/orbsvcs/tests/Miop/McastHello/README +++ b/TAO/orbsvcs/tests/Miop/McastHello/README @@ -1,5 +1,7 @@ /** +$Id$ + @page McastHello Test README File This test verifies basic functionality of the MIOP support in TAO. @@ -20,7 +22,7 @@ users. Firstly, server.cpp includes MIOP.h, which has some magic for loading MIOP protocol in static builds. Secondly, the svc.conf has a directive for loading the right protocol factory. Both of them are required for static builds in addition to linking with the -TAO_PortableGroup library. +TAO_PortableGroup library. However for dynamic builds things are different diff --git a/TAO/orbsvcs/tests/Miop/README b/TAO/orbsvcs/tests/Miop/README index a18f066d6b1..b456d44cfae 100644 --- a/TAO/orbsvcs/tests/Miop/README +++ b/TAO/orbsvcs/tests/Miop/README @@ -1,7 +1,7 @@ $Id$ This directory houses a collection of tests that exercise TAO support -for features defined in the MIOP specification. +for features defined in the MIOP specification. Each individual subdirectory contains a README file with more information on the corresponding test. The list of tests so far diff --git a/TAO/orbsvcs/tests/Security/BiDirectional/README b/TAO/orbsvcs/tests/Security/BiDirectional/README index 14e5d33aaf8..068ef393f4e 100644 --- a/TAO/orbsvcs/tests/Security/BiDirectional/README +++ b/TAO/orbsvcs/tests/Security/BiDirectional/README @@ -1,7 +1,7 @@ -# $Id$ +$Id$ This is a test that exercises the birectional GIOP connection -implementation in TAO over SSLIOP connection. +implementation in TAO over SSLIOP connection. Basicaly, the test is a copy of the $TAO_ROOT/tests/BiDirectional with added support for SSLIOP @@ -9,7 +9,7 @@ added support for SSLIOP Start the server like this $ server -ORBSvcConf server.conf -o <file.ior> -i <no_iterations> -$ client -ORBSvcConf client.conf -k file://<file.ior> -x +$ client -ORBSvcConf client.conf -k file://<file.ior> -x Or, simply @@ -25,5 +25,5 @@ would crash itself. To determine that no new connections have been opened or used the test relies on the fact that TAO uses a transport cache. It can provide us iwith the number of currently cashed transports before and after making an -invocation. Both the client and at the server make this check. +invocation. Both the client and at the server make this check. diff --git a/TAO/orbsvcs/tests/Security/Crash_Test/README b/TAO/orbsvcs/tests/Security/Crash_Test/README index e284c627fd1..46376f1b831 100644 --- a/TAO/orbsvcs/tests/Security/Crash_Test/README +++ b/TAO/orbsvcs/tests/Security/Crash_Test/README @@ -1,9 +1,7 @@ -# -# $Id$ -# +$Id$ This test verifies that the ORB's connection management mechanism is -functioning properly while using SSLIOP as inter-orb protocol. +functioning properly while using SSLIOP as inter-orb protocol. It does so by doing the following: - Starting server with persisten POA. diff --git a/TAO/orbsvcs/tests/Security/MT_IIOP_SSL/README b/TAO/orbsvcs/tests/Security/MT_IIOP_SSL/README index 1c182b4983a..a968a8f68cc 100644 --- a/TAO/orbsvcs/tests/Security/MT_IIOP_SSL/README +++ b/TAO/orbsvcs/tests/Security/MT_IIOP_SSL/README @@ -1,5 +1,7 @@ /** +$Id$ + @page MT_IIOP_SSL Test README File This is a stress test for the IIOP_SSL features. This test should @@ -17,8 +19,8 @@ $ ./run_test.pl the script returns 0 if the test was successful. -@NOTE: - +@NOTE: + This test links *and* loads the SSLIOP library. They are needed due to the way the test is setup. diff --git a/TAO/orbsvcs/tests/Security/MT_SSLIOP/README b/TAO/orbsvcs/tests/Security/MT_SSLIOP/README index 7d695b35da7..ed0e69ffbb4 100644 --- a/TAO/orbsvcs/tests/Security/MT_SSLIOP/README +++ b/TAO/orbsvcs/tests/Security/MT_SSLIOP/README @@ -1,18 +1,18 @@ -# $Id$ +$Id$ Description: - This is a simple test for a thread-pool server that can -service multithreaded clients with the same object reference. + This is a simple test for a thread-pool server that can +service multithreaded clients with the same object reference. It creates a server process with a variable number of threads, -multiple (multithreaded) clients can send requests to it, the +multiple (multithreaded) clients can send requests to it, the requests are handled in different threads. Expected output: The server prints the thread that handles each request. The Client prints the Validation info as well as the thread pid and iteration -number. +number. How to run: Use the run_test.pl. @@ -20,6 +20,6 @@ Use the run_test.pl. FOR SSL:- Pvt Key File ( RSA ) = pvtkey.pem Self Signed Certificate = selfsigncert.pem - + ORB Svc Conf File for Server = server.conf ORB Svc Conf File for Client = client.conf diff --git a/TAO/orbsvcs/tests/Security/Null_Cipher/README b/TAO/orbsvcs/tests/Security/Null_Cipher/README index 7d15e1fb2c7..f46027e282c 100644 --- a/TAO/orbsvcs/tests/Security/Null_Cipher/README +++ b/TAO/orbsvcs/tests/Security/Null_Cipher/README @@ -1,14 +1,12 @@ -# -# $Id$ -# +$Id$ -This test verifies that a NULL cipher may be used. Sometime between +This test verifies that a NULL cipher may be used. Sometime between openssl release 0.9.7a and 0.9.8g, openssl changed the way it evaluated cipher strings so that "DEFAULT:eNULL" no longer allowed use of a NULL cipher. The correction is to have the SSLIOP Factory use "ALL:eNULL" as the cipher string when -SSLNoProtection is used on the server side. -The test is a simple invocation, with qop and trust policies set to +The test is a simple invocation, with qop and trust policies set to force the use of a NULL cipher. A failure is indicated by the server reporting an ssl handshake error. diff --git a/TAO/orbsvcs/tests/Security/mixed_security_test/README b/TAO/orbsvcs/tests/Security/mixed_security_test/README index 422bd9a09d8..67c22d3b92a 100644 --- a/TAO/orbsvcs/tests/Security/mixed_security_test/README +++ b/TAO/orbsvcs/tests/Security/mixed_security_test/README @@ -1,6 +1,4 @@ -# -# $Id$ -# +$Id$ ----------------------------- cases: @@ -13,13 +11,13 @@ cases: This test verifies that the ORB's secure invocation mechanism is functioning properly. It expands on what the Secure_Invocation does -by activating an object with two separate ORBs and POAs. One of the POAs +by activating an object with two separate ORBs and POAs. One of the POAs has a SecQoPNoProtection policy assigned and thus should permit also invocations over non-secure transport. The test verifies that a secure client can make invocations, using both -the "secure" and the "non-secure" IOR from the server. Note that for -the server to support the non-secure invocations it must have -SSLNoProtection +the "secure" and the "non-secure" IOR from the server. Note that for +the server to support the non-secure invocations it must have -SSLNoProtection in its sevice configuration file. The test verifies that a non-secure client can only make invocations through diff --git a/TAO/orbsvcs/tests/Security/ssliop_corbaloc/README b/TAO/orbsvcs/tests/Security/ssliop_corbaloc/README index 6e28b065fb8..73e607e0801 100644 --- a/TAO/orbsvcs/tests/Security/ssliop_corbaloc/README +++ b/TAO/orbsvcs/tests/Security/ssliop_corbaloc/README @@ -1,9 +1,9 @@ -// $Id$ +$Id$ -These application tests address various features of TAO's -Naming Service. The functionality is the same as in the -Simple_Naming test, but the difference is that all the -communication is done over SSLIOP and clients are using +These application tests address various features of TAO's +Naming Service. The functionality is the same as in the +Simple_Naming test, but the difference is that all the +communication is done over SSLIOP and clients are using INS-style corbaloc URLs. To run all tests automatically - @@ -12,12 +12,12 @@ To run all tests automatically - To run tests manually - start the Naming Service (see TAO/orbsvcs/Naming_Service/README for valid options). - Make sure you use " -ORBSvcConf server.conf" and + Make sure you use " -ORBSvcConf server.conf" and "-ORBEndpoint iiop://localhost:23456/ssl_port=12345" - + Then run ./client with one of the options below. Make sure you add " -ORBSvcConf client.conf" and - "-ORBInitRef NameService=corbaloc:ssliop:localhost:12345/NameService" + "-ORBInitRef NameService=corbaloc:ssliop:localhost:12345/NameService" NOTE: if running tests manually, Naming Service has to be restarted before each test (this is due to some tests not 'cleaning up' bindings diff --git a/TAO/orbsvcs/tests/ior_corbaname/README b/TAO/orbsvcs/tests/ior_corbaname/README index 75035230361..40dcceb03a2 100644 --- a/TAO/orbsvcs/tests/ior_corbaname/README +++ b/TAO/orbsvcs/tests/ior_corbaname/README @@ -1,14 +1,14 @@ -// $Id$ +$Id$ -Here is a simple to test the corbaname: style URL. The simple way to -test is to run the run_test.pl. +Here is a simple to test the corbaname: style URL. The simple way to +test is to run the run_test.pl. To test manually: 1. Run the NamingService at a specified endpoint. - + $NamingService -ORBEndPoint iiop://doc.ece.uci.edu:12345 & - + 2. Run the server. ./server & @@ -16,17 +16,17 @@ To test manually: 3. Run the client as one of these. a) ./client corbaname:doc.ece.uci.edu:12345 - - CORBANAME style URL is used and the protocol used to + + CORBANAME style URL is used and the protocol used to contact the naming context is <iiop> implicitly. - + b) ./client corbaname::iiop:doc.ece.uci.edu:12345 - CORBANAME style URL is used and the protocol used to + CORBANAME style URL is used and the protocol used to contact the naming context is <iiop>. - + c) ./client corbaname:rir: - - CORBANAME style URL is used and the protocol used to + + CORBANAME style URL is used and the protocol used to contact the naming context is <rir>. diff --git a/TAO/orbsvcs/tests/tests_svc_loader/README b/TAO/orbsvcs/tests/tests_svc_loader/README index 1e581782879..6348a2463b3 100644 --- a/TAO/orbsvcs/tests/tests_svc_loader/README +++ b/TAO/orbsvcs/tests/tests_svc_loader/README @@ -1,12 +1,12 @@ -// $Id$ +$Id$ This directory contains a generic client program. The program takes an object reference as a commandline parameter and checks if it refers to an existing object and a debug statement is printed out to -reflect the same. +reflect the same. To Run tests_svc_loader ======================= ./tests_svc_loader file://ns.ior - + |