Home

Getting Started

Utilities

Indexing

Omnidex

Development

Tutorials

Quick Links

 

Utilities

ODXNET

Start the Listener

Stop the Listener

 

ODXNET

Directives

Unix

Windows

Pooled Processes

Preconnected Processes

Configuration File

Unix

An ODXNET listener can run on any supported Unix platform interactively or as a daemon process running in the background.

By default, on Unix platforms, ODXNET automatically detaches a forked process from the terminal and becomes a daemon process running in the background independently of the process in which it was started. As long as the original session remains open, child process information will continue to be displayed. When the original session is terminated, the ODXNET daemon process will continue to run until it receives a shutdown command, however the child process information will not be displayed. To prevent the ODXNET listener from running as a daemon process, use the -nodaemon command line directive when starting the listener.

 

 

Start the Listener

To run ODXNET on Unix, start the listener from a command prompt using the -port=n directive along with any of the other command line directives, space separated:

odxnet -port=1232 -nopools

-- or using a configuration file:

odxnet /users/omnidex/bin/odxs1232.cfg

 

Stop the Listener

The ODXNET process can be stopped from within the same server session that it was started in by typing Control + c. It can also be stopped from a separate command prompt by running odxnet with the -port-n and -shutdown directives.

odxnet -port=1232 -shutdown

Use the -delay directive to allow running requests to complete before shutting down the listener.

odxnet -port=1232 -shutdown -delay=30

You can also use the Windows utility NSADMIN to stop a running listener on a Unix server. This method requires a password which can only be defined in the configuration file.

It is important to note that "killing" a listener, stopping it using a method not listed above, could create orphaned processes or other unwanted problems that could affect system performance. Therefore, only kill the listener process as a last resort when all other recommended methods have failed.

 

Top