Path: utzoo!attcan!uunet!fernwood!apple!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!mailrus!cornell!rochester!udel!princeton!notecnirp!drh
From: drh@notecnirp.Princeton.EDU (Dave Hanson)
Newsgroups: comp.windows.x
Subject: xdm/xterm on ncd X terminals
Message-ID: <19290@princeton.Princeton.EDU>
Date: 21 Sep 89 12:19:35 GMT
Sender: news@princeton.Princeton.EDU
Reply-To: drh@princeton.Princeton.EDU (Dave Hanson)
Organization: Dept. of Computer Science, Princeton University
Lines: 14

we've just installed ~50 NCD X windows terminals all connected to a VAX
8650. we use xdm to manage sessions.  we have two problems.

1. xdm isn't up to the job; e.g., cycling power confuses xdm, and
manual initiation of X clients interferes with the xdm session.

2. the xterm's swamp the 8650. with ~70 xterm processes, our load
average shoots to ~25. most users need only a fraction of xterm's
features; a simpler terminal emulator would be useful.

anyone else running similar configurations or have suggestions? (we're
getting some DEC mips boxes, which will help distribute the load.)

replies to drh@princeton.edu. thanx.