Problem
A user is trying to run a Visual Tcl program using
a remote command. For example:# rcmd fusion "DISPLAY=fission:0.0;export DISPLAY;/usr/bin/scoadmin"After quitting the Visual Tcl program, the rcmd(TC) on the local system never exits.
Cause
The first time any Visual Tcl program gets run, a Visual Tcl
server daemon is spawned. In order to improve performance
when executing subsequent Visual Tcl programs, this server
daemon does not die when the original Visual Tcl program
exits. However, rshd(ADMN) on the remote system will not terminate
while it has children (like the server daemon) still running,
and the rcmd(TC) on the local system won't exit until rshd(ADMN)
does.Due to this Visual Tcl architecture, all remote commands after the first will terminate correctly.
Solution
There isn't a safe method to work around this problem using
rcmd(TC). Users should first telnet(TC) into the remote machine,
set their DISPLAY environment variable back to the local machine,
and run the Visual Tcl program.NOTE: The DISPLAY environment variable is automatically set to the local machine when logging into an SCO OpenServer Release 5 system.