The socloc server is a TCP connection oriented iterative server that handles socloc requests. The server is based upon the server IPC API. Note that any mention of QNX in this document refers to the QNX 4.x OS.
In order to use the socloc server, you first must create the socloc startup file which should contain a list of all machines (host names, TCP port numbers and optional IP addresses) that you plan to run the socloc server on. The socloc startup file must be located in the current directory when you execute the program. Remember that a socloc server (upon startup) will search for an entry matching the machine host name.
It is important to remember that the socloc server should be started prior to any socket server or client that requires socloc services. Since the socloc server is assumed to be the first server started within an environment, the server does not send log information to the system log server. All log information is sent to a private/local log file.
The socloc server is a normal process and not a daemon/service.
The socloc server can be compiled for all stated platforms except DOS and QNX where there is no TCP IPC method. Under the Linux/Unix operating systems, the socloc application can be compiled using the mksocloc script.
The socloc server has the following command line syntax:
socloc [-q] [-l log_file]
The optional parameter q is used to have the server run quietly without any console/screen output. The optional parameter l (el) 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 socloc code will be assumed. Note that the switch character (a dash/hyphen [-] is shown here) depends on the platform the application is running on.
Starting in GPL package version 1.33, the socloc server is using the re-written server IPC API which does not close the client socket after sending each reply.