topic Re: X windows in Operating System - HP-UX

X windows

Rob Wallner — Thu, 02 Mar 2006 10:29:16 GMT

Hopefully someone here can help me with this anoying error. I am using exceed to open a window on the HP ux boxes. when I type xterm
I get the following error:

msc00 101: xterm
Error: Can't open display: fh-cae-rxkwrk.matsci.com:0.0
Error: Couldn't find per display information
msc00 102:

any suggestions?

Re: X windows

Arunvijai_4 — Thu, 02 Mar 2006 10:30:39 GMT

Hello,

Could you able to ping from your server to workstation ?

# ping h-cae-rxkwrk.matsci.com

-Arun

Re: X windows

Rick Garland — Thu, 02 Mar 2006 10:38:34 GMT

Are you able to resolve to and from the HPUX system? Are you able to resolve to and from the
fh-cae-rxkwrk.matsci.com system?

What happens if you export your DISPLAY using the IP address of the fh-cae-rxkwrk.matsci.com
system?

Are you getting any X window traffic to your PC?

Re: X windows

Rob Wallner — Thu, 02 Mar 2006 10:38:51 GMT

Yes, pinging is successful

Re: X windows

Rob Wallner — Thu, 02 Mar 2006 10:52:34 GMT

When I export the IP it worked!

when I did a nslookup I get this:

$ /usr/bin/nslookup 172.17.18.131
*** Can't find server name for address 192.168.10.10: No response from server
Using /etc/hosts on: msc00

looking up FILES
Trying DNS
Name: fh-it-rxwlap.matsci.com
Address: 172.17.18.131

I know this sound stupid, where should I look to make sure the DNS servers are pointing to the correct servers?

Re: X windows

Mark Greene_1 — Thu, 02 Mar 2006 11:11:54 GMT

On the HP box, the DNS servers are entered in /etc/resolv.conf

mark

Re: X windows

Rob Wallner — Thu, 02 Mar 2006 14:21:24 GMT

Looks like a lot of the users are using csh.

those users get:
msc00 102: export DISPLAY=172.17.18.107:0.0
export: Command not found.

I do a find / -name export and I can't find the export command.

I have them switch to the sh
and The xterm comes up without the scroll bar

Re: X windows

Bill Hassell — Thu, 02 Mar 2006 15:09:28 GMT

As you will see in the vast majority of comments by sysadmins, csh is to be avoided at all costs. Die-hard programmers like it because it's the only shell they learned, but unless tghe programmer has their own private workstation and doesn't need any help, switch your users to the POSIX shell. Note that ksh is also a POSIX shell but with a few limitations. BASH is also a POSIX shell but not supplied with the Core OS.

There are so many conceptual differences between POSIX shells and csh that it is quite difficult to contrast them. In a POSIX shell, you can find out exactly what a command (like export) is by typing: whence -v export. The POSIX shell will tell you that it is a built-in, or part of the shell.

So if you have to answer all these csh newbie questions, you can either learn csh in depth, or switch your users. Note also that the value for the DISPLAY value may have been set automatically, possibly by parsing the IP or name (fh-cae-rxkwrk.matsci.com) from the who -muR command. The problem is that the user may have used telnet to 'tunnel around' through several servers until arriving on the current one and who -muR reports only the adjacent machine, not the originator of the request. Make sure the DISPLAY variable matches the machine the user is really on.

Re: X windows

Alzhy — Thu, 02 Mar 2006 15:46:04 GMT

For your CSH users:

setenv DISPLAY w.x.y.z:0.0

within Exceed, there should be wizards to automatically set this .