Path: utzoo!attcan!uunet!timbuk!cs.umn.edu!ux.acs!aaron
From: aaron@ux.acs.umn.edu (Aaron Y.T. Cheung)
Newsgroups: comp.windows.x
Subject: OpenWindows shelltool/cmdtool under X-terminal
Keywords: OpenWindows, shelltool/cmdtool, X-terminal
Message-ID: <2522@ux.acs.umn.edu>
Date: 22 Oct 90 06:03:36 GMT
Reply-To: aaron@ux.acs.umn.edu (Aaron Y.T. Cheung)
Organization: University of Minnesota, Academic Computing Services
Lines: 31

We have:

1. Suns running Sun OS 4.1 and OpenWindows 2.0
2. NCD X-terminals under the control of xdm

   Now we want to run the OpenWindows environment (except the NeWS stuffs)
on the X-terminals, and with xdm as the login front end.  Most of the
stuffs work except shelltool/cmdtool.

   Whenever a cmdtool/shelltool is started from _within_ the Olwm pop up
menu (stuffs from .openwin-menu), it get stucked.  A cmdtool/shelltool
window will pop up and what you type will be echoed, but nothing from
the system.  I do a "ps ux" from another terminal and see that the
/bin/csh process that was spawned by the shelltool was in T (stopped)
state.  I tried "kill -CONT pid" but no good.

   If I login to another terminal, "setenv DISPLAY ncd:0; shelltool",
everything works fine.

   Actually, I think the same thing happen if I use the olwm/shelltool
distributed by MIT.  However, they worked alright back in the days of
Sun OS 4.0.3.

   All in all, shelltool/cmdtool (MIT and OpenWindows) screw up when
called up from within Olwm, on Sun OS 4.1.

   Any help will be very much appreciated.


PS:  Xdm reports the following when the problem occurred:
     ttysw-TIOCSPGRP: Interrupted system call