rtmon

Name

rtmon — start the SmartSockets monitoring process RTmon

Synopsis

rtmon [ -command pathname ] [ -help ] [ -nofork ] [ -runtime ]  

Arguments

-command pathname — alternate startup command file to use (default is rtmon.cm in current directory).

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

-nofork — do not automatically fork rtmongdi process.

-runtime — do not attempt to start the GDI version of RTmon (on platforms that support it); instead just start the command-line version.

Return Values

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

Description

The rtmon script starts the SmartSockets monitoring process RTmon. For a complete description of RTmon, see the TIBCO SmartSockets User’s Guide.

The default behavior of RTmon is to attempt to start the GUI version of itself. This interface is implemented as a separate process (rtmongdi). When RTmon starts, it forks (starts) the rtmongdi process and attempts to connect to it. If RTmon is unable to connect to the GDI process, it will switch to command-line mode instead. If started with -runtime, RTmon goes directly to command-line mode and does not start the mongdi process.

The GUI version of RTmon (rtmongdi) has been deprecated and may be removed in a future release.

When first invoked, RTmon looks for the license startup command file. This file contains settings for license-related options used by RTmon to obtain a license during the startup process. The filename and directory location of the startup command file is:

$RTHOME/standard/license.cm 

RTHOME:[STANDARD]LICENSE.CM 

%RTHOME%\standard\license.cm 

The behavior of RTmon is determined by the values set for the various RTmon options, which are read from up to three levels of rtmon.cm startup command files. For more information about the startup command file, refer to the TIBCO SmartSockets User’s Guide.

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

The -nofork argument prevents RTmon from automatically forking (starting) the rtmongdi script when RTmon is in development mode. This is useful for debugging rtmon and rtmongdi separately (usually only useful for source code licenses).

The -runtime argument starts RTmon in command-line mode and does not attempt to start or use the rtmongdi graphical interface.

The rtmon script runs the RTmon executable. On UNIX, rtmon is a symbolic link to the generic SmartSockets startup script rtprocess. On OpenVMS rtmon is not a script but a symbol.

The rtmon script starts the standard RTmon from the SmartSockets installation directory.

Caution

None

See Also

rtmongdi, rtserver

Examples

/* start rtmon with a different startup command file */ 
$ rtmon -command file.cm 
/* start run-time RTmon */ 
$ rtmon -runtime 
/* start development RTmon, but do not start rtmongdi */ 
$ rtmon -nofork