Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ncar!gatech!mailer.cc.fsu.edu!uflorida!bikini!ajg
From: ajg@reef.cis.ufl.edu (Arnold Goldberg)
Newsgroups: comp.windows.x
Subject: xlock crashes on remote NCD terminals
Message-ID: <AJG.91Jun22183105@reef.cis.ufl.edu>
Date: 22 Jun 91 22:31:05 GMT
Sender: news@uflorida.cis.ufl.EDU
Distribution: comp
Organization: Computer Science Department/ University of Florida
Lines: 34


I've recently installed xlock PL 2.2.

The problem that occurs whenever I try to run it on an Xncd terminal is

X Error: BadAccess
	Major code 111()
	Minor code 0
	ResourceID 0x400000004
	Error Serial #170
	Current Serial# 176

at that point I can no longer get access to my NCD X-server (maybe the xhost maps are
gone?), and I have to reboot it.

Here area the operating parameters:

NCD Xservers 16 or 17 I believe.
xlock running on Sun SS1, 4.1.1

xlock is installed setuid root (as it's supposed to be)
i'm invoking xlock w/ -remote.


Help please

Thanks.

Arnold

--
#include <disclaimer.h>

Arnold Goldberg				IP: ajg@reef.cis.ufl.edu