rtmongdi

This script has been deprecated and may be removed in a future release.

Name

rtmongdi— start the SmartSockets RTmon GDI process

Synopsis

rtmongdi [ -help ] [ -pid ProcessID ] 

Arguments

-help — print a brief synopsis of the valid command-line arguments and exit

-pid ProcessID — specify process ID of RTmon process to communicate with

Return Values

On UNIX and Windows, rtmongdi returns 0 if successful, and a non-zero value otherwise. On OpenVMS, rtmongdi returns an odd value (usually 1) if successful, and an even value otherwise.

Description

The rtmongdi implements the RTmon GDI. It is normally not necessary to run rtmongdi by itself, as RTmon normally starts rtmongdi as a child process, automatically.

When rtmongdi starts, it normally uses the process ID of its parent process (the RTmon process) to create a connection to the RTmon process (the process ID is used to build a local connection name).

The -help argument causes rtmongdi to print a brief synopsis and exit.

The -pid argument is needed when rtmongdi is started manually (such as when both rtmon and rtmongdi are being run under the control of a debugger). The ProcessId should be specified as the process ID of the RTmon process. It is also necessary to start the RTmon process first with the -nofork argument (so that the RTmon process is ready to accept a connection from the rtmongdi process).

See Also

rtmon

Examples

To start rtmon and rtmongdi separately, use this method. In one terminal emulator window, start RTmon with the -nofork option.

$ rtmon -nofork 
 
SmartSockets banner information 
. 
. 
. 
My process ID is 9356. 
Starting development environment. Please wait. 
Waiting for up to 20 seconds for GDI process to connect. 

The RTmon process is waiting for an rtmongdi process to connect to it.

The RTmon only waits for a limited amount of time. If the time-out period is reached and no rtmongdi process has connected, the RTmon process automatically switches to run-time mode.

In another terminal emulator window, start rtmongdi (using the PID printed by the RTmon process).

$ rtmongdi -pid 9356 
..Using pid <9356>. 
....done. 

When rtmon and rtmongdi are started separately, the output that normally appears in the scrollable text window appears instead in the window where the RTmon process is started. This is to allow easier debugging of the two processes.