| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
Is there any reason why session manager would not run down all the
processes when Quiting? I have a customer who has a PVAX with
VMS5.1-B. They occasionally notice a performance problem when logging
in and when we do a SHOW SYS, there is a process running eating
up CPU cycles. It's process name is userid$vue_1, which I can produce
by selecting a DCL command from the FileView Utility menu option.
If I dismiss that Task Block, rather than Stop Task, that process
hangs around. However, on a good day when I quit via the session
manager, it kills all processes. On random occasions, one of these
vue processes sticks around eating CPU cycles, Under what circumstances
would a process hang in there even though I've quit my session manger.
MArgi LaGrotta
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 649.1 | WSINT::MCLEMAN | Jeff McLeman | Fri Apr 21 1989 08:09 | 6 | |
This is strange, since the VUE$framitz_1 processes are children of the parent vue process. When you quit the session, the server resets, breaking connections, which should cause the processes to be run down, including the children. Don't know why, unless the process is above IPL 0 and can't be deleted for some reason. What application did the user run under vue? | |||||
| 649.2 | STAR::BENSON | Mon Apr 24 1989 10:00 | 28 | ||
.1 is correct that FileView's subprocesses are called VUE$username_n.
The session manager creates FileView with the process name
username_VUEn.
When you hit Dismiss in a Task Output box, you're only making the box
pop down - not stopping the task it's running. If you start a COPY with
LOG specified, FileView will pop up the Task Output box showing the
LOG output. If you Dismiss the box, the COPY is still running. You can
see the progress of the COPY in the Work in Progress box, and get the
Task Output box back by selecting the task in the list and hitting the
Show Output button. If you hit Stop Task, however, the COPY will
terminate. However, even in this case, the subprocess will stay around.
FileView re-uses subprocesses for later tasks.
When you exit FileView, or log out via the Session Manager, all these
subprocesses should go away. The only exception I've seen is if FileView
crashes for some reason. (RE: .1 - the subprocs have no direct connection
to the server, unless the task being run is a DECwindows application. For
things like DCL Command, Search, etc, the main process handles all the
I/O.)
If there's a reproducible problem with a FileView subprocess surviving
after the user logs out, please QAR it. Include info about what the
subprocess was running.
Tom
| |||||
| 649.3 | Re-defined LOGOUT? | CSC32::K_OGLESBY | Fri Apr 28 1989 17:20 | 13 | |
Have you redefined the verb LOGOUT to do something kinky that the
VUE process might not understand? If so, the command procedure
that is input to the procedure would do:
$ on_error then goto done
.
.
.
$ done:
$ logout and loop forever
Kelly
| |||||
| 649.4 | It Won't Loop | CSC32::K_OGLESBY | Fri Apr 28 1989 17:52 | 2 | |
Check that ... it won't loop forever, but it won't log out either. | |||||