Examples, Recommendations on command console implementation, Using running applications – Visara Master Console Center Administration Guide User Manual
Page 97: Using scripts, Signal handling
Chapter 5 MCC system.cfg Configuration File
Administration Guide
97
Examples
The following example provides console consolidation of a Windows NT server
through Netscape Navigator installed on the MCC. The VNC executable must be
installed on the NT server.
[console NTServer]
interface=command
command=netscape http://NTServer:5800
categories=Command
The following example displays the index of the MCC manuals in a Netscape
Navigator browser on the MCC workstation.
[console MCC Manuals]
interface=command
command=netscape file:/usr/ics/etc/doc/manual/html/index.html
categories=Command
The following example runs an X-windows application called xeyes from the
command console.
[console xeyes]
interface=command
command=exec /usr/bin/X11/xeyes
categories=Command
Recommendations on Command Console Implementation
Using Running Applications
The command must handle multiple requests for the same command console.
This functionality is supported by some applications such as Netscape Navigator,
which has a “-remote openURL(…)” option to use an existing Netscape process.
Refer to examples/commandconsoles/reuse-netscape for more information.
Using Scripts
Whenever possible, implement a command console by calling a script instead of a
command, as it avoids the need to restart the MCC to reread the configuration
file.
Signal Handling
Some applications such as xterm do not exit when SIGHUP is received. In such
cases, use a script that forwards signals to a child process. The child process
takes the same environment variables as the parent. Refer to
examples/commandconsoles/map-signals for a sample script. Since gwconsole
(the process that runs the console window) kills child processes on exit, the
application should be defined as the child process. However, gwconsole uses ksh
to run the command to allow shell quoting, so do one of the following: