Aravind Gottipati wrote: > -SNIP- <
One thing I noticed that wasdifferent between xdm on NetBSD and Debian was that NetBSD stored all its xdm configs in /usr/X11R6/lib/X11/xdm, but Debian stores it both in /usr/X11R6/lib/X11/xdm and /etc/X11/xdm (they refer to each other and its a mess in debian). Could this be a possible cause?
Dunno...I know for a fact that XDM works here in the Debian way of doing things, so I would suspect something else is going on than just the differences in the two types of X.
I did an strace on the process when it was locked up
and taking about 95% CPU and I found that it was stuck
in some kind of select loop. Here is an excerpt from
the output.
gettimeofday({1041297960, 882864}, NULL) = 0
select(256, [1 3 9 10 11], NULL, NULL, {292, 114000})
= 1 (in [3], left {292, 120000})
read(3, "", 64) = 0
gettimeofday({1041297960, 883119}, NULL) = 0
select(256, [1 3 9 10 11], NULL, NULL, {292, 113000})
= 1 (in [3], left {292, 120000})
read(3, "", 64) = 0
--- SIGALRM (Alarm clock) ---
setitimer(ITIMER_REAL, {it_interval={0, 0},
it_value={0, 0}}, NULL) = 0
sigreturn() = ? (mask now
[])
setitimer(ITIMER_REAL, {it_interval={0, 20000},
it_value={0, 20000}}, NULL) = 0
gettimeofday({1041297960, 883974}, NULL) = 0
select(256, [1 3 9 10 11], NULL, NULL, {292, 113000})
= 1 (in [3], left {292, 120000})
read(3, "", 64) = 0
gettimeofday({1041297960, 884240}, NULL) = 0
select(256, [1 3 9 10 11], NULL, NULL, {292, 112000})
= 1 (in [3], left {292, 120000})
read(3, "", 64) = 0
gettimeofday({1041297960, 884495}, NULL) = 0
select(256, [1 3 9 10 11], NULL, NULL, {292, 112000})
= 1 (in [3], left {292, 120000})
read(3, "", 64) = 0
gettimeofday({1041297960, 884750}, NULL) = 0
select(256, [1 3 9 10 11], NULL, NULL, {292, 112000})
= 1 (in [3], left {292, 120000})
read(3, "", 64) = 0
This is greek to me <grin>. As I said, I am NOT a programmer, but from what I see it definately appears you are right. I have no idea what it is trying to do here... except it has something to do with time... How is your system clock working??
I fully agree the "problem" is probably in the XDM package...or something it depends upon rather than in X. This is especially true since your "startx" command works alright, IMHO.
Donald: I don't mind working offline, would you be on OPN by any chance?
I don't know what "OPN" stands for...that probably means that I am not on it! I am suscribed to this list, have the E-Mail address above, and have both AIM and YAHOO IM clients here. I am on RoadRunner too, if that makes any difference.
I just took a look at the package numbering between "testing" and "unstable" for XDM and they don't appear to be all that much different. Version 4.2.1-3 for "testing" and version 4.2.1-4 for "unstable". BTW, you can have GDM, KDM, and XDM all installed at the same time and select which one you want to use now. I have all three currently installed on my system, but am using GDM at the moment. I'll change over to XDM temporarily to make sure we are on the same sheet of music.
For starters, why don't you try a re-install of XDM (apt-get --reinstall install xdm) and re-check that you have all the dependencies present? You might have to go through each one manually to make sure.
Are you just trying to get XDM working as a display manager for a single computer? I really don't know where to start, so feel free to start asking for comparisons if you wish. My Video card is a Voodoo 3000 (3D Labs...uses the tdfx driver module)
Cheers, -Don Spoon-