Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!haven!udel!rochester!kodak!isctsse!kadsma!fuller
From: fuller@kadsma.kodak.COM (Bill Fuller)
Newsgroups: comp.windows.x
Subject: xlock hanging problems on Sun 4/280
Keywords: xlock bug
Message-ID: <1990Aug29.175912.2638@usenet@kadsma>
Date: 29 Aug 90 17:59:12 GMT
Sender: usenet@usenet@kadsma (News Administrator)
Reply-To: fuller@kadsma.kodak.COM (Bill Fuller)
Organization: Eastman Kodak Telecommunication Services, Rochester, N.Y. 14650
Lines: 26

Hi,

	I have been running X windows on all of our Sun platforms since
R2.  I have had no problems with any of our stations (which includes
386i's SUN 4/110 SUN 3/110 and Sparc 1's) running X except for one
lonely 4/280.  The configuration for this box is as follows:

SUN 4/280
SunOS 4.0.3
40 Meg RAM
2 Eagle Hard drives.
1 1/2 in tape
1 exabyte.
	
	Anyways, here is the problem....If a user uses xlock on this host,
it will quickly hangup, not allow the user to get back in.  I have tried to
attach to the process with dbx, but dbx gets hung during the reading of
the symbol
table.  The process will not respond to any of the core dumping signals, and
eventually, you end up having to kill the thing with a -9.  Needless to say,
the usual user of this station is quite upset...Can anyone help shed some light
onto this matter?

William H. Fuller		Dial: (716)-726-2311
Senior Systems Consultant	UUCP: ...!rochester!kodak!kadsma!fuller
Rochester, N.Y.			ARPA: fuller@kadsma.kodak.com