dumsocks GPL Application

The dumsocks server is a really dumb connection oriented iterative server using either TCP sockets or QNX native message passing. The server is based upon the server IPC API. This server and the dumsockc client were built to verify and test the socloc server. Note that any mention of QNX in this document refers to the QNX 4.x OS.

In order to use the dumsocks server, you first must create the socloc startup file which should contain a list of suggested socloc servers. The list may be incomplete but at least one entry must describe an active socloc server. The socloc startup file must be located in the current directory when you execute the program.

The dumsocks server requires at least one socloc server to be responding. It is important to remember that the socloc server should be started prior to any socket server or client that requires socloc services. The dumsocks server logs information either to a private log file or to the system log server. Note that the QNX version of this application does not use or require socloc.

The dumsocks server accepts a limited number of commands including all common socket codes. The dumsockc client application implements all dumsocks commands.

The dumsocks server is a normal process and not a daemon/service.

The dumsocks server can be compiled for all stated platforms except DOS where there is no TCP IPC method. Under the Linux/Unix/QNX operating systems, the dumsocks application can be compiled using the mkdumsocks script.

# Command Line Syntax

The dumsocks server has the following command line syntax:

    TCP: dumsocks [-q] [-l log_file] port
    QNX: dumsocks [-q] [-l log_file]

Where port is the TCP port that the dumsocks server should listen to. The optional parameter q is used to have the server run quietly without any console/screen output. The optional parameter l is used to specify an output log file name. If the log file name is not specified, the default log file name given in the dumsocks code will be assumed. Note that the switch character (a dash/hyphen [-] is shown here) depends on the platform the application is running on.

Goto Top | Future Lab Home | Contact Webmaster | Feedback

Copyright © 2000-2006 Future Lab, Last Updated Jun 25, 2006