The CommuniGate Pro Server supports the following command-line options (parameters):
The next parameter string specifies the location of the CommuniGate Pro base directory.
This option tells the Server to duplicate all its System Log records to the stdout (standard output). This option can be used for troubleshooting when the Web interface to System Logs is not available.
This option tells the Server to ignore all current Log Level settings and record all possible Log records.
This option can be specified on Unix platforms only. It tells the Server to fork and operate in the background, with stdin, stdout, and stderr redirected to /dev/null.
The next parameter string specifies the location of the CommuniGate Pro application directory. You can use this option when the application itself cannot properly detect its own location, or if the CommuniGate Pro Server application file is not placed in the same location as other application directory files and subdirectories. For example, on OS/400 CommuniGate Pro Server is located in an OS/400 library, and this parameter is used to tell the server where the Unix-style directory with WebUser, WebAdmin, WebGuide, and other files is located.
See the Network section for the details.
This option tells the Server not to try to lock the ProcessID lock file. This option can be used if the file system hosting the base directory does not support file locks.
This option can be specified on Unix platforms only (this does not include Linux). It tells the Server to drop the root privilege permanently. The server drops the privilege approximately 60 seconds after the end of its kernel initialization process, so all listening sockets can be opened when the server is still running as the root. The root privilege cannot be restored later. See the Server Root Privilege section for more details.
This option tells the Server to sleep for the specified number of seconds before proceeding with initialization. This option can be used when CommuniGate Pro starts during system startup and it should let other services to startup fully (for example, an external file system can be mounted, a virtual IP address can be created, etc.)
This option can be specified on platforms supporting p-threads (OS/400 and most Unix flavors). The next parameter string can be either "system" or "process". See your OS manual to learn how these "scheduling scopes" work. If this option is not specified, the default OS scheduling mode is used.
This option can be specified on Microsoft Windows platforms only. The option tells the Server to use 'batch logon' instead of the 'network logon' when an account password is verified using the Windows OS password system.
This option can be specified on Microsoft Windows and IBM OS/2 pla