Article View: comp.windows.x
Article #24057xlock problem on NCD terms
From: Arnold Goldberg
Date: Tue, 25 Jun 1991 18:05
Date: Tue, 25 Jun 1991 18:05
31 lines
1212 bytes
1212 bytes
In summary to the xlock crashing on NCD terminals, here are the correct answers: ---------------------------------------------------------------------- From: rauletta@sitevax.gmu.edu (R. J. Auletta) I use -remote and -allowaccess (I believe it is -allowaccess or +allowaccess) and that seems to work just dandy. Without the allowaccess the xhost list goes away and no new clients can connect including xhost. -R J Auletta ---------------------------------------------------------------------- From: klein@ncd.com (ncdu11) You don't have to reboot - simply go into the SETUP menus , under 'Network Parameters', and turn off TCP/IP access control. Doug klein@ncd.com -- #include <disclaimer.h> Arnold Goldberg IP: ajg@reef.cis.ufl.edu
Technical Details
Message-ID:
<AJG.91Jun25140506@reef.cis.ufl.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!uflorida!bikini!ajgShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!uflorida!bikini!ajg From: ajg@reef.cis.ufl.edu (Arnold Goldberg) Newsgroups: comp.windows.x Subject: xlock problem on NCD terms Message-ID: <AJG.91Jun25140506@reef.cis.ufl.edu> Date: 25 Jun 91 18:05:06 GMT Sender: news@uflorida.cis.ufl.EDU Distribution: comp Organization: Computer Science Department/ University of Florida Lines: 32