linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Glynn Clements <glynn@gclements.plus.com>
To: Luca Ferrari <fluca1978@infinito.it>
Cc: linux-admin@vger.kernel.org
Subject: Re: hp xterm
Date: Mon, 8 Nov 2004 09:05:33 +0000	[thread overview]
Message-ID: <16783.14045.420042.833614@cerise.gclements.plus.com> (raw)
In-Reply-To: <200411071244.59060.fluca1978@infinito.it>


Luca Ferrari wrote:

> > > I've trying to get a few HP 700/RX terminal working, but I'm not very
> > > experienced with them and I'm encountering a problem. The software is
> > > installed over a suse 9.1 server, and the terminal connects rightly thru
> > > tftp to the server downloading the code. However, after the whole
> > > process, the xterm shows me the x cursor (the classical 'X') and the
> > > standard x background, and nothing more. I mean, no login prompt, no
> > > windows are displayed. The server is configured to accept xdmcp calls,
> > > but I cannot get the xterm working. Any idea about? I'm running kdm as
> > > login manager.
> >
> > Does the X terminal use XDMCP? Is there any record (in the log files)
> > of an XDMCP request being sent? 
> 
> I think so, but I'm not really experienced about them. However, in the log I 
> found the following:

[snip]

> and nothing in the messages. Xinetd stores only things about tftp, that seems 
> to work rightly. The following are my configuration files:

> lx01:~ # cat /opt/kde3/share/config/kdm/kdmrc

> [Xdmcp]
> # Whether KDM should listen to XDMCP requests. Default is true.
> Enable=true

> Any idea?

Realistically, I think that you are going to need to use tcpdump (or
ethereal etc) to check that the terminals are actually sending out
XDMCP requests. If they aren't, no amount of server-side configuration
will have any effect.

Once you've determined that XDMCP requests are actually being sent,
you can look into the server-side configuration.

If you can't get the terminals to issue XDMCP requests, the only
solution is to forcibly manage them, by adding them to the Xservers
file. This requires that the terminals are started before xdm/kdm.

-- 
Glynn Clements <glynn@gclements.plus.com>

      reply	other threads:[~2004-11-08  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-04  8:45 hp xterm Luca Ferrari
2004-11-05  5:11 ` Glynn Clements
2004-11-07 11:44   ` Luca Ferrari
2004-11-08  9:05     ` Glynn Clements [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16783.14045.420042.833614@cerise.gclements.plus.com \
    --to=glynn@gclements.plus.com \
    --cc=fluca1978@infinito.it \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).