Hi Pete,
Thanks for the info, but let me explain in detail the thing
I am trying to do.
I have installed Informatica Power analyzer, a Data warehouse reporting tool
on a Linux Box. The application is running on jBoss server. There are
servlets that create charts. The web server enables users to access these
charts through a browser throughout the network. Now this servlet needs X
windows server for the charts display, so they connect to the X server by
the display variable localhost:0, but unfortunately this is not happening,
and that's why those error messages. It was working fine till I tried to
change the hostname of the Linux box. I have reverted back to old settings
but things are not working yet. I am not familiar with Linux environment to
a great extent, so I was trying to find a way to set the display variable so
that the servlet accesses the server, regarding the lock files, where should
I go and delete them????
Regards
Santhosh
-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx
[mailto:redhat-list-bounces@xxxxxxxxxx]On Behalf Of Pete Nesbitt
Sent: Thursday, June 24, 2004 6:06 PM
To: General Red Hat Linux discussion list
Subject: Re: Problems in setting display variable for X Windows server
On June 24, 2004 12:00 pm, santhosh wrote:
> Hi,
> Thanks for the suggestions, but I should have informed you that
> a) I have logged in as root directly into the window using a ssh
connection
> (putty)
> b) I have tried to put things back....its still not working....
>
> Here is some info I gathered.....I heard that if an
> user is logged into the X server and opened a connection....nobody else
can
> open another connection.....so I am wondering if something got messed
> up...and though nobody is using the connection...the server still has some
> files left behind to believe that someone else is using the connection
>
>
>
> Regards,
> Santhosh
If you are ssh'ing in to run X, you can't do that. You want to log in via
ssh
launched from an X terminal on your local machine. Then in the ssh session
execute the X app you want to run on the remote machine and it will be
displayed locally.
The X server can run lots of sessions at once, that's why it is a server :)
There can only be one instance of a X server running per display (not the
actual monitor), that is why you want to remove any old lock files that may
have been created on any of the failed X startups (as your error message
indicated).
In X, the server is your local keyboard, mouse and video, while the client
is
the remote application. So when you run "xhost +" it should be on your local
machine, to allow _any_ machine to display it's X application on your local
machine. I don't think you'll need to do that though, as ssh should take
care
of X forwarding (which I beleive is on by default).
Hope that helps.
--
Pete Nesbitt, rhce
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
