🚀 go-pugleaf

In article <7166@fluke.COM> jeff@tc.fluke.com (Jeff Stearns) writes:
+casey@lll-crg.llnl.gov (Casey Leedom) writes:
+>  [text deleted]
+>We use standard ascii terminals as the consoles of all our file servers.
+>After the systems have been up for a while, the terminals lock up and we
+>haven't figured out how to break them out of that mode....
+
+    - Don't ever suntools to run on the server.  Some folks try to start up
+      suntools from .login; this will of course fail on your server.  In
+      the process, it will wedge the console.

We have several 3/160s that operate as a fileserver and suntools
workstation at the same time, for over a year now with no lockup problems.
Besides the packing style of the 160s and 180s, is there some other
difference I am not aware of?

@ Christopher  M.  Meier   ms:  MN65-2300   Honeywell Systems & Research Center
@ SIP/AIT                  (612) 782-7191   3660 Technology Drive
@ meier@SRC.Honeywell.COM  !SRCSIP!meier    Mpls, MN  55418

[[ I think they were referring to "headless" servers, or a server that
uses /dev/ttya as its console.  Some people fire up suntools straight from
their .login.  If they log into the console of a machine that has no
bitmap display and no mouse, suntools start up anyway and promptly wedges
the console.  I wonder if using the emergency keyboard exit, CTRL-D and
CTRL-Q, would make suntools go away in such a situation.  Has anyone tried
that (see the sunview(1) manual page if you don't know what I'm talking
about)?  --wnl ]]