Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!mcvax!unido!exunido!dewal
From: dewal@exunido.UUCP
Newsgroups: comp.os.vms
Subject: Stopped Processes on the GPX - (nf)
Message-ID: <137900001@exunido.UUCP>
Date: Tue, 12-May-87 09:41:00 EDT
Article-I.D.: exunido.137900001
Posted: Tue May 12 09:41:00 1987
Date-Received: Fri, 29-May-87 01:39:32 EDT
Lines: 24
Nf-ID: #N:exunido:137900001:000:1080
Nf-From: exunido!dewal    May 12 14:41:00 1987

University of Dortmund
Department of Computer Science
Software Technology Laboratory

We have got a MicroVax II (GPX). Several times it occured that proces-
ses started on the graphic display stopped. At this point we were not
able to use the graphic screen anymore. Trying to kill the processes lo-
cated on the graphic screen failed. We had to reboot the system to use the
graphic screen. At the first time we were lucky to login from an other
terminal as system user to perform a shutdown. The other time we even 
could not log into the system anymore. The only possiblity left was to
switch off the whole system. 
There were not many processes active when this problem occured. So it can-
not be that an overload is responsible for this error.
Why cannot the superuser kill the processes ? Is it not possible to kill
processes located on the console (as the graphic display is also console
device) ? How can we proceed when this error occurs, because I think that
switching off the power is not a good solution.

Thanks

Sanjay Dewal

(dewal@unido.uucp or dewal@exunido.uucp)