| Title: | POLYCENTER Console Manager |
| Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
| Moderator: | CSC32::BUTTERWORTH |
| Created: | Thu Aug 06 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1541 |
| Total number of notes: | 6564 |
From a VAXstation 4000/VLC running OpenVMS V5.5-2 and UCX V2.0D, we need to remotely activate a csh script on a DECstation 5000/240 running ULTRIX V4.3 to run the /usr/bin/cm -C3 POLYCENTER Console Manager (CM) and redirect the CM X-display back to the VLC screen. To accomplish the latter, we currently place the following command in OPTIONS within SESSION MANAGER on the VLC: @sys$pcm:cm_fire The cm_fire.com consists of the following line where gec039 is the target ULTRIX node and gec031 is the VLC node: $ rsh gec039/user="henry"/lower "cm_fire gec031:0.0" In the henry user account on node gec039, the cm_fire csh script consists of the following lines, where the "gec031:0.0" is passed to the $1 argument: #!/bin/csh setenv DISPLAY $1 /usr/bin/cm -C3 Problem: For some reason, by maintaining the rsh session, the C3 daemon sometimes enters a "process looping" state - a killer that prevents other daemon processes from executing! We need to make rsh activate C3 and then release the network connection immediately to solve this problem! We need to allow an operator to click his mouse on a CM Motif menu option which activates the @sys$pcm:cm_fire DCL command procedure with the following results: 1) rsh activates the cm_fire script on the ULTRIX system 2) rsh, having accomplished its mission, releases the network connection 3) C3 runs as a "detached" process whose display gets redirected back to the VLC 4) The C3 X-display appears on the VLC screen WITHOUT an additional Fileview window! Any ideas? If you are not running the CM software, then simply substitute the /usr/bin/dxclock application in the above scenario. No theories please...we need a proven tested solution to this note! Frustrated beyond belief... This topic is posted in three conferences: POLYCENTER CONSOLE MANAGER UCX ULTRIX \Thanks in Advance!
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 163.1 | Did the shell script I sent not work then?? | OPG::SIMON | Sun Jan 16 1994 19:13 | 8 | |
Tom,
I sent a couple of shell scripts in a mail to you which invoke
the C3 via rsh, but attach stdin and stdout to /dev/null. Are these
not appropriate? Although I have not tried this rsh method from UCX to
ULTRIX, it certainly detached a C3 and exited the rsh beteen ULTRIX and
ULTRIX.
Cheers SImon....
| |||||
| 163.2 | Fileview Window Appears Problem | LTLKNG::ZIGLER | Tom Zigler DTN:432-7541 | Mon Jan 17 1994 14:01 | 27 |
Simon,
Yes, your suggested csh script worked just fine as far as running C3 in
the background and immediately releasing the rsh connection. However,
in the process, an additional Fileview window pops up with:
[1] 17653
Unfortunately, I have yet to figure out a way to stop this additional
Fileview window from appearing. The suggestions that I have received
in the other VAX Notes conferences have not worked either thus far
(UCX, ULTRIX conferences).
For use by operations staff, I must achieve the following results in an
attempt to prevent the C3 "process looping" problem:
1) Operator invokes C3 display as a Motif menu option
2) C3 executes in background
3) rsh link releases
4) C3 display redirected to VMS workstation
5) No Fileview window appears
6) Operator can interact with the redirected C3 display
Any ideas? The appearance of the additional Fileview window is NOT
acceptable for use by operators!
\Thanks in Advance
| |||||
| 163.3 | OPG::SIMON | Mon Jan 17 1994 14:06 | 5 | ||
Tom
try the sh version of the script I gave you as that does not report
the backgrounded job's PID.
Cheers Simon......
| |||||
| 163.4 | C3 Still Process Looping | LTLKNG::ZIGLER | Tom Zigler DTN:432-7541 | Thu Jan 20 1994 21:29 | 17 |
Simon,
The new cm_fire Bourne shell script you sent me works great now.
However, the C3 displays are still periodically entering a "process
looping" condition, even though the rsh connection is immediately
relinquished once the C3 display has been redirected.
This problem is also occurring at our other CMC site.
Any ideas as to how we can solve this continuing "process looping"
problem? This problem is serious because eventually, if these looping
C3 processes are not killed, other daemons do not get enough CPU time
to execute.
Please advise.
\Thanks in Advance
| |||||