[comp.sys.sun] Problems running sunview after X11R4

mferrare@sirius.ucs.adelaide.edu.au (Mark Ferraretto) (11/21/90)

I have had the following problem for a few months:

We have here sun 3/60s running sunOS 4.0.3 running dataless.  Their /usr
partition is exported from a sun 4/280 running sunOS 4.0.3.  Lately we
have found that sometimes when we run sunview not all the command tools
and the console window show up.  Using top we find that the tools are
running and are usually taking up an exorbitant amount of the cpu.  A lot
of the people have complained that this happens after the previous user
has used X windows.  Initially I thought this could not be possible but
now I've found some things that may indicate the opposite:

When users exit from X, the terminals they were using (ie ttyp1 ttyp2 etc)
when they were running X still show up when they type finger.

So it looks like X exits but doesn't clean up after itself properly.
Let's take the following scenario:

User-a runs X and starts up several x-terms and then exits (usually by
selecting Exit from twm as this is the last process running in .xinitrc
for most of them) and logs out.  user-b logs in and tries to start
sunview.  All his mailtools, clocks, textedits and dvipage previewers come
up OK but no command tools or shell tools.  He exits and types finger and
sees something like the following:

Login       Name              TTY Idle    When    Where
cbridge  Chris Bridge          co      Thu 18:22
mferrare Mark Ferraretto       p1   1d Wed 14:45  unix:0.0
mferrare Mark Ferraretto       p2   1d Wed 14:50  unix:0.0
mferrare Mark Ferraretto       p3   1d Wed 16:41  unix:0.0
and so on.

Let us assume that ttyp0-6 are taken by mferrare.  cbridge starts up
sunview again and this time asks for command tools until they appear.  He
types:

tty
and gets:
ttyp7

This implies to me that command tools (and shelltools) aren't starting
because the slots ttyp0-7 are taken by mferrare.  This means that X isn't
exiting properly.  Incidentally, when mferrare started sunview up after
having run X there was no problem.  This seems to imply an ownership
problem with the ttyp* Is this the case?  What can I do to fix it?

Many thanks.  I'll summarise if interest warrants
Mark Ferraretto