fuller@kadsma.kodak.COM (Bill Fuller) (08/30/90)
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
naughton@wind.Eng.Sun.COM (Patrick Naughton) (08/31/90)
|>> fuller@kadsma.kodak.COM (Bill Fuller) writes: |> 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 |> |> 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 -- I have had about a dozen reports of xlock "hanging" for mysterious reasons over the last year... I recently rewrote most of it to support multiple screens and xrm and in the process removed a lot of redundant sigblock(2), and sigsetmask(2) calls, which seems to have made the problem disappear on the one machine here at Sun where it was happening... Watch this space for an announcement of source availability for this latest version of xlock... (Septemberish) -Patrick ______________________________________________________________________ Patrick J. Naughton ARPA: naughton@sun.com Window Systems Group UUCP: ...!sun!naughton Sun Microsystems, Inc. AT&T: (415) 336 - 1080