Digital UNIX 3.2c and XDM: limit on number of managed terminals?

From: Niels Kokholm <kokholm_at_math.ku.dk>
Date: Thu, 30 Nov 1995 15:03:38 +0100 (MET)

We are running a network of DEC workstations (mips and alpha) and NCD
Xterminals. We have a problem with an alphastation 250 4/266
running Digital UNIX 3.2c.

(jessen:~/> uname -a
OSF1 jessen V3.2 148 alpha)

If you have a solution to the following problem, please mail to me, I
will summarize. I prefer a DEC patch for compiling some version of xdm
myself. I have asked my local DEC reseller to solve the problem.

The X terminals get a xdm chooser list containing a.o. "jessen" from
another host ("zeuthen").
1) When less than 6 X-terminals are currently
managed by xdm on "jessen" (i.e. are logged in og has a login box from
jessen), the next terminal choosing jessen gets a login screen as it
should.
2) When 6 terminals are currently managed by "jessen", other
terminals choosing jessen does not get a login screen, but gets the
chooser list back after a (long) while. (If one of the other already managed
X-terminals logs out during this period, the login screen appears
immediately.)
This practical limit of 6 terminals seems quite reproducible on jessen,
but does not occur on the other alphas (running DEC OSF/1 3.0).

The xdm-errors file contains a lot of lines like this
error (pid 469): Unknown session exit code 2816 from process 7528
error (pid 469): Unknown session exit code 2816 from process 10075
error (pid 469): Unknown session exit code 2816 from process 12977
error (pid 469): Unknown session exit code 2816 from process 10900
error (pid 469): Unknown session exit code 2816 from process 8005
error (pid 469): Unknown session exit code 2816 from process 32383

(Twenty for each failed login it seems, which seems to fit with the
default openRepeat and startAttempts xdm resources).

Running xdm in debug mode gives a lot of output, the following snippet
shows where things go wrong:
---------------------------------------------------------------------
DisplayManager.rosa_0.userAuthDir/DisplayManager.NCD-19r.UserAuthDir
value /tmp
DisplayManager.rosa_0.chooser/DisplayManager.NCD-19r.Chooser value
/usr/bin/X11
/chooser
DisplayManager.rosa_0.language/DisplayManager.NCD-19r.Language value
DisplayManager.rosa_0.autoLogin/DisplayManager.NCD-19r.AutoLogin value
pid: 15968
signals blocked, mask was 0x0
Manager wait returns pid: 15968 sig 11 core 0 code 0
Display exited with unknown status 2816
StopDisplay: rosa:0
WaitForSomething
select returns 1. Rescan: 0 ChildReady: 0
ProcessRequestSocket
header: 1 13 6
Send alive
alive: 1 7
------------------------------------------------------------------------
This is an example, where things go right
------------------------------------------------------------------
DisplayManager.kirsten_0.userAuthDir/DisplayManager.NCD-19c.UserAuthDir
value /t
mp
DisplayManager.kirsten_0.chooser/DisplayManager.NCD-19c.Chooser value
/usr/bin/
X11/chooser
DisplayManager.kirsten_0.language/DisplayManager.NCD-19c.Language value
DisplayManager.kirsten_0.autoLogin/DisplayManager.NCD-19c.AutoLogin value
LANG is
Before XOpenDisplay(kirsten:0)
pid: 12466
WaitForSomething
After XOpenDisplay(kirsten:0)
Got remote address kirsten:0 16
ManageSession kirsten:0
LANG is
Loading resource file: /usr/var/X11/xdm/Xresources
ManageSession: loading greeter library /usr/shlib/X11/libXdmDecGreet.so
greet kirsten:0
----------------------------------------------------------------------
It seems to me, that the child xdm process exits abnormally, but I don't
have the sourcecode for the version of xdm shipped by DEC, so some of the
debug output is hard to follow.



   Niels Jørgen Kokholm | email: kokholm_at_math.ku.dk
   Matematisk Institut | phone: +45 3532 0759
   Universitetsparken 5
   DK-2100 København Ø
   Denmark
Received on Thu Nov 30 1995 - 15:51:36 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:46 NZDT