diff options
Diffstat (limited to 'TAO/orbsvcs/Naming_Service/README')
| -rw-r--r-- | TAO/orbsvcs/Naming_Service/README | 88 |
1 files changed, 46 insertions, 42 deletions
diff --git a/TAO/orbsvcs/Naming_Service/README b/TAO/orbsvcs/Naming_Service/README index c6f84e5ddf6..7030d444f6a 100644 --- a/TAO/orbsvcs/Naming_Service/README +++ b/TAO/orbsvcs/Naming_Service/README @@ -13,17 +13,18 @@ The following describes how to run the TAO Naming Service. 1. Syntax % Naming_Service [-ORBNameServicePort nsport] + [-b base_address] + [-d ] + [-f persistence_file_name] + [-m (1=enable multicast responses,0=disable(default)] + [-n number_of_threads] [-o ior_output_file] [-p pid_file_name] + [-r directory] [-s context_size] [-t time] - [-f persistence_file_name] - [-b base_address] - [-m (1=enable multicast responses,0=disable(default)] - [-z time] - [-d ] [-u directory] - [-r directory] + [-z time] 2. Optional Command-line Arguments @@ -34,23 +35,15 @@ The following describes how to run the TAO Naming Service. use of multicast. This is only used when multicast responding is enabled via '-m 1'. - -o ior_output_file - The name of the file, in which to store the IOR of the - root Naming Service context. - - -p pid_file_name - The name of the file, in which to store the process id - of the Naming Service server. - - -s context_size - Size of the hash table allocated for the root Naming - Context (if one is created). All contexts created - under the root will use the same size for their hash - tables. The default is 1024. + -b base_address + The address used for memory mapping the file specified + with the "-f" option above. The value supplied with + this option is only used when the Naming Service runs + in persistent mode, i.e., "-f" option is present. - -t time - How long (in seconds) the server should listen for - client requests before terminating. + -d + Provides Naming Service specific debug information. By default + no diagnostics are given. -f persistence_file_name The name of the file to use to store/retrieve @@ -58,12 +51,6 @@ The following describes how to run the TAO Naming Service. option, Naming Service is started in non-persistent mode. - -b base_address - The address used for memory mapping the file specified - with the "-f" option above. The value supplied with - this option is only used when the Naming Service runs - in persistent mode, i.e., "-f" option is present. - -m <0|1> TAO offers a simple, very non-standard method for clients to discover the initial reference for the @@ -74,29 +61,46 @@ The following describes how to run the TAO Naming Service. such multicast queries (use the Interoperable Naming Service bootstrap options instead). - -z time - A relative round trip timeout value (in seconds) that - the service should wait for when trying to progress an - operation through a federated naming context before - timing out and throwing a 'Cannot proceed' exception - to the client. If no value is set this will never occur. + -n number_of_threads + Specify a number of threads to be used to run the ORB. + Default is 1. - -d - Provides Naming Service specific debug information. By default - no diagnostics are given. + -o ior_output_file + The name of the file, in which to store the IOR of the + root Naming Service context. - -u directory - Use a flat-file persistence implementation that stores object - reference information in a file per context. Each context file - is placed in the directory specified. + -p pid_file_name + The name of the file, in which to store the process id + of the Naming Service server. + + -s context_size + Size of the hash table allocated for the root Naming + Context (if one is created). All contexts created + under the root will use the same size for their hash + tables. The default is 1024. + + -t time + How long (in seconds) the server should listen for + client requests before terminating. -r directory - Use redundant flat-file persistnece; same as the -u option, + Use redundant flat-file persistence; 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). + -u directory + Use a flat-file persistence implementation that stores object + reference information in a file per context. Each context file + is placed in the directory specified. + + -z time + A relative round trip timeout value (in seconds) that + the service should wait for when trying to progress an + operation through a federated naming context before + timing out and throwing a 'Cannot proceed' exception + to the client. If no value is set this will never occur. 3. Environment Variables |